Wireless communication method, terminal device and network device

Abstract

The embodiment of the application provides a wireless communication method, a terminal device and a network device, the method comprises the following steps: acquiring configuration information of an uplink interval; repeatedly transmitting uplink information on an uplink channel according to the configuration information of the uplink interval; wherein the uplink interval is used for the terminal device to perform downlink synchronization and frequency offset compensation on the uplink interval, so as to adapt to a non-GEO scene in an NTN network.

Description

Technical Field

[0001] This application relates to the field of communications, and more specifically, to a wireless communication method, terminal device, and network device. Background Technology

[0002] Narrowband Internet of Things (NB-IoT) networks support uplink channels including the Narrowband Physical Random Access Channel (NPRACH) and the Narrowband Physical Uplink Shared Channel (NPUSCH). Due to the repetitive transmission mechanism introduced in NPRACH and NPUSCH, and because NB-IoT terminals only support half-duplex type-B mode (meaning terminal devices can only receive or transmit data at any given time), an uplink (UL) gap is introduced for longer uplink transmissions. This uplink gap is primarily used for synchronization tracking and frequency offset (crystal oscillator frequency shift) compensation using the Narrowband Primary Synchronization Signal (NPSS), Narrowband Secondary Synchronization Signal (NSSS), or Narrowband Reference Signal (NRS).

[0003] Currently, the uplink interval is predefined in the protocol. Because NB-IoT terminals have low mobility, and base stations are stationary in terrestrial networks, the channel quality of NB-IoT terminals typically changes slowly. Therefore, defining the uplink interval using a predefined method is reasonable.

[0004] However, in non-terrestrial networks (NTNs), especially in geostationary Earth orbit (GEO) scenarios, the wireless signal transmission delay between the terminal device and the network changes continuously due to the rapid movement of satellites, even when the terminal device is stationary. Furthermore, the wireless channel variation patterns between terminal devices and the network located at different orbital altitudes under GEO satellite coverage differ. Additionally, because the coverage area of ​​an NTN network is much larger than that of a terrestrial network, the wireless channel variation patterns between terminal devices located at different geographical locations within the same cell also differ. Therefore, using a predefined uplink spacing method is not suitable for non-GEO scenarios in NTN networks. Summary of the Invention

[0005] This application provides a wireless communication method, a terminal device, and a network device to adapt to non-GEO scenarios in NTN networks.

[0006] In a first aspect, a wireless communication method is provided, comprising: acquiring configuration information of uplink intervals; repeatedly transmitting uplink information on the uplink channel according to the configuration information of uplink intervals; wherein the uplink interval is used by the terminal device to perform downlink synchronization and frequency offset compensation in the uplink interval.

[0007] Secondly, a wireless communication method is provided, comprising: acquiring uplink interval configuration information; repeatedly transmitting uplink information on the uplink channel according to the uplink interval configuration information; wherein the uplink interval is used by the terminal device to perform TA pre-compensation or TA adjustment on the uplink interval.

[0008] Thirdly, a wireless communication method is provided, comprising: transmitting uplink interval configuration information; wherein the uplink interval is used by the terminal device to perform downlink synchronization and frequency offset compensation in the uplink interval.

[0009] Fourthly, a wireless communication method is provided, comprising: transmitting uplink interval configuration information; wherein the uplink interval is used by the terminal device to perform TA pre-compensation or TA adjustment in the uplink interval.

[0010] Fifthly, a terminal device is provided for executing the methods in the first aspect, the second aspect, or their respective implementations described above.

[0011] Specifically, the terminal device includes a functional module for performing the methods described in the first aspect, the second aspect, or their respective implementations.

[0012] Sixthly, a network device is provided for performing the methods in the third, fourth, or other implementations thereof described above.

[0013] Specifically, the network device includes a functional module for performing the methods in the third aspect, the fourth aspect, or their respective implementations described above.

[0014] In a seventh aspect, a terminal device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the methods described in the first aspect, the second aspect, or their respective implementations.

[0015] Eighthly, a network device is provided, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program stored in the memory to perform the methods in the third, fourth, or other implementations thereof described above.

[0016] Ninthly, an apparatus is provided for implementing the method in any one of the first to fourth aspects or their respective implementations.

[0017] Specifically, the device includes a processor for calling and running a computer program from memory, causing a device equipped with the device to perform the method as described in any of the first to fourth aspects or their respective implementations.

[0018] In a tenth aspect, a computer-readable storage medium is provided for storing a computer program that causes a computer to perform the methods of any one of the first to fourth aspects or their respective implementations.

[0019] Eleventhly, a computer program product is provided, including computer program instructions that cause a computer to perform the methods of any one of the first to fourth aspects or their respective implementations.

[0020] In a twelfth aspect, a computer program is provided that, when run on a computer, causes the computer to perform the methods of any one of the first to fourth aspects or their respective implementations.

[0021] In this application, the uplink interval configuration information is not predefined, but is configured by the network device to the terminal device, which can realize the difference of the uplink interval configuration information for different terminal devices, so as to adapt to non-GEO scenarios in NTN networks.

[0022] In this application, the terminal device can also insert uplink intervals into the uplink transmission according to the configuration information of the uplink interval to perform TA pre-compensation or TA adjustment. Therefore, regardless of whether the TA decreases or increases, the terminal device can accurately perform TA pre-compensation or TA adjustment, as well as uplink transmission. Attached Figure Description

[0023] Figure 1 This is a flowchart illustrating the four-step random access process based on competition.

[0024] Figure 2 This is a schematic diagram of time synchronization on the gNB side provided in an embodiment of this application;

[0025] Figure 3A This application provides a schematic diagram of the architecture of a communication system.

[0026] Figure 3B This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application;

[0027] Figure 4 An interactive flowchart of a wireless communication method provided in an embodiment of this application;

[0028] Figure 5A A schematic diagram illustrating the configuration of the uplink interval corresponding to NPRACH provided in the embodiments of this application;

[0029] Figure 5B A schematic diagram illustrating the configuration of the uplink interval corresponding to the NPUSCH provided in this application embodiment;

[0030] Figure 6 A schematic diagram illustrating the relationship between the preamble, the first uplink interval, and the random access response window provided in an embodiment of this application;

[0031] Figure 7 A schematic diagram illustrating the relationship between the preamble, the first uplink interval, and the random access response window provided in yet another embodiment of this application;

[0032] Figure 8 A schematic diagram illustrating the relationship between the preamble, the first uplink interval, and the random access response window, provided in yet another embodiment of this application;

[0033] Figure 9 A schematic block diagram of a terminal device 900 according to an embodiment of this application is shown;

[0034] Figure 10 A schematic block diagram of a terminal device 1000 according to an embodiment of this application is shown;

[0035] Figure 11 A schematic block diagram of a network device 1100 according to an embodiment of this application is shown;

[0036] Figure 12 A schematic block diagram of a network device 1200 according to an embodiment of this application is shown;

[0037] Figure 13 This is a schematic structural diagram of a communication device 1300 provided in an embodiment of this application;

[0038] Figure 14 This is a schematic structural diagram of the device according to an embodiment of this application;

[0039] Figure 15 This is a schematic block diagram of a communication system 1500 provided in an embodiment of this application. Detailed Implementation

[0040] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. All other embodiments obtained by those skilled in the art without creative effort regarding the embodiments of this application are within the scope of protection of this application.

[0041] Before introducing the technical solution of this application, the relevant knowledge of this application will be explained below:

[0042] I. Background Information on NTN

[0043] The 3rd Generation Partnership Project (3GPP) is currently researching NTN technology, which typically uses satellite communication to provide communication services to terrestrial users. Compared to terrestrial cellular communication, satellite communication has many unique advantages. First, satellite communication is not limited by user location. For example, conventional terrestrial communication cannot cover oceans, mountains, deserts, or other areas where communication equipment cannot be installed or where there is no communication coverage due to sparse population. However, with satellite communication, a single satellite can cover a large area, and since satellites orbit the Earth, theoretically every corner of the Earth can be covered by satellite communication. Second, satellite communication has significant social value. Satellite communication can provide coverage in remote mountainous areas and impoverished countries or regions at a relatively low cost, enabling people in these areas to enjoy advanced voice communication and mobile internet technologies, helping to narrow the digital divide with developed regions and promoting development in these areas. Third, satellite communication has a long range, and the cost does not increase significantly with increasing communication distance. Finally, satellite communication is highly stable and is not affected by natural disasters.

[0044] Communication satellites are classified according to their orbital altitude into Low-Earth Orbit (LEO) satellites, Medium-Earth Orbit (MEO) satellites, GEO satellites, Highly Elliptical Orbit (HEO) satellites, and so on. Currently, research primarily focuses on LEO and GEO.

[0045] LEO

[0046] Low Earth orbit (LEO) satellites have an altitude range of 500km to 1500km, with corresponding orbital periods of approximately 1.5 to 2 hours. The signal propagation delay for single-hop communication between users is generally less than 20ms. The maximum satellite visibility time is 20 minutes. The short signal propagation distance and low link loss mean that the requirements for user terminal transmission power are not high.

[0047] GEO

[0048] A geostationary orbit satellite, with an orbital altitude of 35,786 km, orbits the Earth every 24 hours. The signal propagation delay for single-hop communication between users is typically 250 ms.

[0049] To ensure satellite coverage and improve the overall capacity of the satellite communication system, satellites use multi-beam coverage to cover the ground. A single satellite can generate dozens or even hundreds of beams to cover the ground; a single satellite beam can cover a ground area with a diameter of tens to hundreds of kilometers.

[0050] II. Uplink Interval for NB-IoT Terminals

[0051] As mentioned above, the uplink channels supported by the NB-IoT network include NPRACH and NPUSCH. NPRACH is used to transmit the preamble. NPUSCH supports two formats: format1 and format2. NPUSCH format1 is used for uplink data transmission, while NPUSCH format2 is used to transmit Hybrid Automatic Repeat Request-Acknowledgement (HARQ-ACK) feedback information.

[0052] Because a repetitive transmission mechanism is introduced on NPRACH and NPUSCH, the maximum number of repetitive transmissions can reach 2048. However, since NB-IoT terminals only support FDD half-duplex type-B mode, meaning the terminal device can only receive or send data at any given time, not simultaneously, an uplink (UL) gap is introduced for longer uplink transmissions. This uplink gap is primarily used for synchronization tracking and frequency offset (crystal oscillator frequency shift) compensation using NPSS, NSSS, or NRS signals.

[0053] Currently, the uplink interval is predefined in the protocol. Specifically:

[0054] For NPUSCH: 256ms of data is transmitted, with frequency offset compensation performed through a 40ms uplink interval.

[0055] For NPRACH: After transmitting 64 preambles, frequency offset compensation is performed through an uplink interval of 40ms.

[0056] III. Random Access Procedures in Long Term Evolution (LTE) Systems Figure 1 This is a flowchart illustrating the four-step random access process based on competition.

[0057] like Figure 1 As shown, the random access procedure may include the following four steps:

[0058] Step 1, Msg 1.

[0059] The terminal device sends Msg 1 to the network device to inform the network device that the terminal device has initiated a random access request. Msg 1 carries a Random Access Preamble (RAP), also known as a random access preamble sequence, preamble, or preamble code. Simultaneously, Msg 1 can also be used by the network device to estimate the transmission delay between itself and the terminal device and to calibrate the uplink time accordingly.

[0060] Specifically, the terminal device selects a preamble index and a PRACH resource for sending the preamble; then, the terminal device transmits the preamble on the PRACH. The network device notifies all terminal devices via a System Information Block (SIB) that the preamble is permitted to be transmitted on which time-frequency resources, for example, SIB1.

[0061] Step 2, Msg 2.

[0062] After receiving Msg 1 from the terminal device, the network device sends Msg 2, which is the Random Access Response (RAR) message, to the terminal device. This Msg 2 may carry, for example, Time Advance (TA), uplink authorization instructions such as uplink resource configuration, and Temporary Cell-Radio Network Temporary Identity (TC-RNTI).

[0063] The terminal device listens on the Physical Downlink Control Channel (PDCCH) within the Random Access Response (RAR) window to receive RAR messages from the network device. These RAR messages can be descrambled using the corresponding Random Access Radio Network Temporary Identifier (RA-RNTI).

[0064] If the terminal device does not receive a reply RAR message from the network device within the RAR window, the random access process is considered to have failed.

[0065] If the terminal device successfully receives a RAR message, and the preamble index carried in the RAR message is the same as the index of the preamble sent by the terminal device via Msg 1, then the RAR is considered to have been successfully received, and the terminal device can stop listening within the RAR window.

[0066] Msg 2 may include RAR messages for multiple terminal devices. Each terminal device's RAR message may include the random access preamble identifier (RAP Identify, RAPID) used by the terminal device, information on resources used to transmit Msg 3, TA adjustment information, TC-RNTI, etc.

[0067] Step 3, Msg 3.

[0068] After receiving a RAR message, the terminal device determines whether it is its own RAR message. For example, the terminal device can use a preamble identifier for verification. After confirming that it is its own RAR message, the terminal device generates Msg3 at the RRC layer and sends Msg3 to the network device. Msg3 needs to carry the terminal device's identification information, etc.

[0069] Specifically, for different random access trigger events, Msg 3 in step 3 of the 4-step random access process can include different content for scheduled transmission.

[0070] For example, in the initial access scenario, Msg 3 may include an RRC connection request generated by the RRC layer, which carries at least the Non-Access Stratum (NAS) identification information of the terminal device, and may also carry, for example, the Serving-Temporary Mobile Subscriber Identity (S-TMSI) or a random number of the terminal device.

[0071] For example, in a connection reconstruction scenario, Msg 3 may include an RRC Connection Re-establishment Request generated by the RRC layer without carrying any NAS message. In addition, it may carry information such as Cell Radio Network Temporary Identifier (C-RNTI) and Protocol Control Information (PCI).

[0072] For example, in a handover scenario, Msg 3 may include an RRC handover confirmation message generated by the RRC layer and the terminal device's C-RNTI, and may also carry, for example, a buffer status report (BSR); for other triggering events such as the arrival of uplink / downlink data, Msg 3 must at least include the terminal device's C-RNTI.

[0073] Step 4, Msg 4.

[0074] The network device sends Msg 4 to the terminal device, and the terminal device correctly receives Msg 4 to complete the contention resolution. For example, during the establishment of an RRC connection, Msg 4 can carry an RRC connection establishment message.

[0075] Since the terminal device in step 3 carries its unique identifier in Msg 3, such as C-RNTI or identification information from the core network (such as S-TMSI or a random number), the network device will carry the unique identifier of the terminal device in Msg 4 to designate the winning terminal device in the contention resolution mechanism. Other terminal devices that do not win the contention resolution will re-initiate random access.

[0076] In current LTE systems, considering the transition time between transmit and receive operations of the terminal device, the terminal device initiates the RAR window after a certain interval following the transmission of Msg1. For NB-IoT terminals, the starting subframe of the RAR window is n+X, where n is the last subframe containing the last repeated transmission of the preamble, and the value of X is determined based on Time Division Duplex (TDD) or FDD, and the number of NPRACH repeated transmissions. Specifically, the value of X can be determined using Table 1.

[0077] Table 1

[0078]

[0079] It should be noted that in this application, the random access response window (RAR window) is also referred to as the RAR receive window, RAR time window, etc., and this application does not limit it.

[0080] IV. Timing Advance (TA) Mechanism in NR Systems:

[0081] A key characteristic of uplink transmission is orthogonal multiple access in time and frequency domains for different terminal devices, meaning that uplink transmissions from different terminal devices within the same cell do not interfere with each other. To ensure the orthogonality of uplink transmissions and avoid intra-cell interference, network devices require that signals from different terminal devices originating from the same time but using different frequency domain resources arrive at the network device at essentially the same time. To ensure time synchronization on the network device side, NR supports the uplink TA mechanism.

[0082] Figure 2 This is a schematic diagram of time synchronization on the gNB side provided in an embodiment of this application, as shown below. Figure 2 As shown in the left-hand diagram, without the TA mechanism, the uplink and downlink clocks on the UE side are the same. For a downlink symbol transmitted by the gNB side, due to the different propagation delays between different UEs and the gNB, the uplink data from different UEs arrives at the gNB side at asynchronous times. For example... Figure 2 As shown in the attached diagram on the right, there is an offset between the uplink clock and the downlink clock on the UE side, and different UEs have their own different uplink TA values, which introduces the TA mechanism. By appropriately controlling the TA value corresponding to each UE, the gNB can control the arrival time of uplink data from different UEs at the gNB, so as to synchronize the arrival time of uplink data from different UEs at the gNB side and synchronize it with the downlink timing on the gNB side. Specifically, for UEs farther away from the gNB, due to the larger transmission delay, uplink data must be sent earlier than that of UEs closer to the gNB.

[0083] The gNB determines the TA value for each UE based on measurements of the UE's uplink transmissions. The gNB sends TA commands to the UE in two ways.

[0084] Acquisition of the initial TA: During the random access procedure, the gNB determines the TA value by measuring the received preamble and sends it to the UE through the Timing Advance Command field of the RAR.

[0085] TA Adjustment in RRC Connected State: Although the UE and gNB achieve uplink synchronization during random access, the timing of the uplink signal arriving at the gNB may change over time. Therefore, the UE needs to continuously update its uplink TA value to maintain uplink synchronization. If a UE's TA value needs correction, the gNB will send a Timing Advance Command to that UE, requesting it to adjust its TA value. This Timing Advance Command is sent to the UE via the Timing Advance Command MAC CE.

[0086] As mentioned above, since NB-IoT terminals have low mobility and base stations are stationary in terrestrial networks, the channel quality of NB-IoT terminals usually changes slowly. Therefore, it is more reasonable to define the uplink interval using a predefined method.

[0087] However, in NTN networks, for non-GEO scenarios, even when the terminal device is stationary, the wireless signal transmission delay between the terminal device and the network constantly changes with the rapid movement of the satellite. Furthermore, on the one hand, the wireless channel variation patterns between terminal devices and the network under the coverage of non-GEO satellites at different orbital altitudes are different; on the other hand, because the coverage area of ​​an NTN network is much larger than that of a terrestrial network, the wireless channel variation patterns between terminal devices located at different geographical locations within the same cell and the network are also different. Therefore, using a predefined uplink spacing method is not suitable for non-GEO scenarios in NTN networks.

[0088] To address the aforementioned technical issues, this application can configure different uplink intervals for different NB-IoT terminals to suit non-GEO scenarios in NTN networks.

[0089] The following is combined Figures 3A-3B The architecture of the communication system in this application will be described.

[0090] Figure 3A This is a schematic diagram of the architecture of a communication system provided in an embodiment of this application. Please refer to [link / reference]. Figure 3AThis includes terminal device 1101 and satellite 1102, which can communicate wirelessly. The network formed between terminal device 1101 and satellite 1102 can also be called an NTN. Figure 3A In the architecture of the communication system shown, satellite 1102 can function as a base station, and terminal device 1101 and satellite 1102 can communicate directly. In this system architecture, satellite 1102 can be referred to as a network device. Optionally, the communication system may include multiple network devices 1102, and the coverage area of ​​each network device 1102 may include other numbers of terminal devices; this embodiment does not limit this.

[0091] Figure 3B This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application. Please refer to... Figure 3B The network includes terminal device 1201, satellite 1202, and base station 1203. Terminal device 1201 and satellite 1202 can communicate wirelessly, and satellite 1202 can communicate with base station 1203. The network formed by terminal device 1201, satellite 1202, and base station 1203 can also be called an NTN. Figure 3B In the architecture of the communication system shown, satellite 1202 may not function as a base station, and communication between terminal device 1201 and base station 1203 requires relay through satellite 1202. In this system architecture, base station 1203 can be referred to as a network device. Optionally, the communication system may include multiple network devices 1203, and the coverage area of ​​each network device 1203 may include other numbers of terminal devices; this embodiment does not limit this.

[0092] Optionally, Figures 3A-3B The wireless communication system shown may also include other network entities such as a Mobility Management Entity (MME) and an Access and Mobility Management Function (AMF), but this application does not limit this.

[0093] It should be understood that the terms "system" and "network" are often used interchangeably in this article.

[0094] Optionally, the communication system in this application embodiment can be applied to a carrier aggregation (CA) scenario, a dual connectivity (DC) scenario, or a standalone (SA) network deployment scenario.

[0095] Optionally, the embodiments of this application can be applied to unlicensed spectrum or licensed spectrum. Unlicensed spectrum can also be considered as shared spectrum, and licensed spectrum can also be considered as non-shared spectrum.

[0096] This application describes various embodiments in conjunction with network devices and terminal devices, wherein: the terminal device can be an NB-IoT terminal or a non-NB-IoT terminal, and the terminal device in this application can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device, etc.

[0097] In the embodiments of this application, the terminal device can be deployed on land, including indoor or outdoor, handheld, wearable or vehicle-mounted; it can also be deployed on water (such as ships); and it can also be deployed in the air (such as airplanes, balloons and satellites).

[0098] Alternatively, the network equipment can be a base station, such as Figure 3B As shown, network devices can also have mobility characteristics; for example, a network device can be a mobile device, such as... Figure 3A As shown. Optionally, the network equipment can be a satellite or a balloon station. For example, the satellite can be a LEO satellite, MEO satellite, HEO satellite, etc. Optionally, the network equipment can also be a base station located on land, water, or other similar locations.

[0099] In this embodiment, the network device can provide services to a cell. The terminal device communicates with the network device through the transmission resources (e.g., frequency domain resources, or spectrum resources) used by the cell. The cell can be the cell corresponding to the network device (e.g., a base station). The cell can belong to a macro base station or to a base station corresponding to a small cell. The small cell can include: metro cell, micro cell, pico cell, femto cell, etc. These small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-speed data transmission services.

[0100] The technical solution of this application will be described in detail below:

[0101] Example 1

[0102] Figure 4 An interactive flowchart of a wireless communication method provided in an embodiment of this application is shown below. Figure 4 As shown, the method includes the following steps:

[0103] S410: The terminal device obtains the configuration information of the uplink interval, wherein the uplink interval is used by the terminal device to perform downlink synchronization and frequency offset compensation in the uplink interval.

[0104] S420: The terminal device repeatedly transmits uplink information on the uplink channel according to the configuration information of the uplink interval.

[0105] Optionally, the configuration information for the uplink interval may be carried in any of the following, but not limited to: broadcast messages, Radio Resource Control (RRC) signaling, Media Access Control Element (MAC CE), or Downlink Control Information (DCI).

[0106] Optionally, the configuration information for the uplink interval includes: the duration of the uplink interval, and / or, the insertion interval of the uplink interval; wherein, an uplink interval appears after each continuous insertion interval of the uplink channel.

[0107] For example, Figure 5A This is a schematic diagram illustrating the configuration of the uplink interval corresponding to NPRACH provided in the embodiments of this application, as shown below. Figure 5A As shown, after each continuous insertion interval X1, NPRACH has an uplink interval of duration Y1. Figure 5B This is a schematic diagram illustrating the configuration of the uplink interval corresponding to the NPUSCH provided in the embodiments of this application, as shown below. Figure 5B As shown, after each continuous insertion interval X2, NPUSCH has an uplink interval of duration Y2.

[0108] It is worth mentioning that this application does not restrict how network devices determine the duration of uplink intervals, and / or the insertion interval of uplink intervals.

[0109] Optionally, the uplink interval duration can be predefined, and the network device only needs to configure the uplink interval insertion interval to the terminal device. Alternatively, the uplink interval insertion interval can be predefined, and the network device only needs to configure the uplink interval duration to the terminal device.

[0110] Optionally, the network device can also send uplink channel resource configurations to the terminal device.

[0111] Optionally, the resource configuration of the uplink channel may be carried in any of the following, but not limited to: broadcast message, RRC signaling, MAC CE, DCI.

[0112] Optionally, the aforementioned uplink channel can be NPRACH or NPUSCH, but is not limited to these.

[0113] Optionally, if the uplink channel is NPRACH, the aforementioned uplink information may be a preamble transmitted on NPRACH. If the uplink channel is NPUSCH, the aforementioned uplink information may be uplink data transmitted on NPUSCH or HARQ-ACK feedback information.

[0114] Optionally, when a network device broadcasts NPRACH resource configurations via a broadcast message, it can broadcast or configure resource configurations for at least one NPRACH at a time. Based on this, the uplink interval configuration information is configuration information for at least one NPRACH; that is, the aforementioned uplink interval configuration information can correspond to one NPRACH resource or multiple NPRACH resources. For example, the uplink interval configuration information can be configured separately for each set of NPRACH resources, or all NPRACH resources can use the same uplink interval configuration information.

[0115] Optionally, the resource configuration for each NPRACH may include at least one of the following, but is not limited to: the period of the NPRACH, the start time of the NPRACH resource within a period, the starting subcarrier position of the NPRACH resource, the number of consecutive subcarriers occupied by the NPRACH resource in the frequency domain, and the number of times the preamble is repeatedly transmitted.

[0116] In summary, in this application, the uplink interval configuration information is not predefined, but is configured by the network device to the terminal device, which can realize the difference in uplink interval configuration information for different terminal devices, so as to adapt to non-GEO scenarios in NTN networks.

[0117] Example 2

[0118] In non-GEO scenarios within NTN networks, the RTT changes rapidly, requiring terminal devices to frequently adjust the TA. For uplink transmissions with numerous repetitions, terminal devices also need to continuously adjust the TA during these repetitions. When the TA decreases, the terminal device can simultaneously perform TA adjustment and uplink transmission; however, when the TA increases, the terminal device cannot perform both simultaneously.

[0119] To address the aforementioned technical issues, in this application, the network device can also configure uplink interval configuration information for the terminal device. When the uplink channel is NPRACH, the uplink interval configuration information is used by the terminal device to perform timing advance pre-compensation on that uplink interval. When the uplink channel is NPUSCH, the uplink interval configuration information is used by the terminal device to perform timing adjustment on that uplink interval.

[0120] It should be noted that TA pre-compensation is calculated by the terminal device and is the TA compensation that the terminal device needs to perform during random access.

[0121] It should be understood that this TA pre-compensation is also referred to as TA compensation, TA pre-compensation value, etc., and this application does not limit it.

[0122] Optionally, when the uplink channel is NPUSCH, the terminal device can perform TA adjustment according to the TA adjustment command or based on the terminal device's own TA compensation capability.

[0123] It should be noted that both TA adjustment and TA pre-compensation involve the terminal device adjusting its TA. When sending Msg1 during random access, the terminal device does not yet have a valid TA, so TA pre-compensation is performed. When the terminal device is in connected state, it maintains a TA and can adjust it.

[0124] Optionally, in this embodiment, the configuration information of the uplink interval is carried in any of the following, but not limited to: broadcast message, RRC signaling, MAC CE, DCI.

[0125] Optionally, in this embodiment, the configuration information of the uplink interval includes: the duration of the uplink interval, and / or, the insertion interval of the uplink interval. Wherein, the uplink channel experiences one uplink interval after each insertion interval.

[0126] It is worth mentioning that this application does not restrict how network devices determine the duration of uplink intervals, and / or the insertion interval of uplink intervals.

[0127] Optionally, the uplink interval duration can be predefined, and the network device only needs to configure the uplink interval insertion interval to the terminal device. Alternatively, the uplink interval insertion interval can be predefined, and the network device only needs to configure the uplink interval duration to the terminal device.

[0128] Optionally, the network device can also send uplink channel resource configurations to the terminal device.

[0129] Optionally, the resource configuration of the uplink channel may be carried in any of the following, but not limited to: broadcast message, RRC signaling, MAC CE, DCI.

[0130] Optionally, the aforementioned uplink channel can be NPRACH or NPUSCH, but is not limited to these.

[0131] Optionally, when a network device broadcasts NPRACH resource configurations via a broadcast message, it can broadcast or configure resource configurations for at least one NPRACH at a time. Based on this, the uplink interval configuration information is configuration information for at least one NPRACH; that is, the aforementioned uplink interval configuration information can correspond to one NPRACH resource or multiple NPRACH resources. For example, the uplink interval configuration information can be configured separately for each set of NPRACH resources, or all NPRACH resources can use the same uplink interval configuration information.

[0132] Optionally, the resource configuration for each NPRACH may include at least one of the following, but is not limited to: the period of the NPRACH, the start time of the NPRACH resource within a period, the starting subcarrier position of the NPRACH resource, the number of consecutive subcarriers occupied by the NPRACH resource in the frequency domain, and the number of times the preamble is repeatedly transmitted.

[0133] In summary, in this application, for non-GEO scenarios in NTN networks, the terminal device can insert uplink intervals during uplink transmission based on the aforementioned uplink interval configuration information to perform TA pre-compensation or TA adjustment. Therefore, regardless of whether the TA decreases or increases, the terminal device can accurately perform TA pre-compensation or TA adjustment, as well as uplink transmission.

[0134] It should be noted that, for convenience, when the uplink channel is NPRACH and the uplink interval is used by the terminal device for downlink synchronization and frequency offset compensation in that uplink interval, this uplink interval is called the first uplink interval; when the uplink channel is NPRACH and the uplink interval is used by the terminal device for TA pre-compensation in that uplink interval, this uplink interval is called the second uplink interval; when the uplink channel is NPUSCH and the uplink interval is used by the terminal device for downlink synchronization and frequency offset compensation in that uplink interval, this uplink interval is called the third uplink interval; and when the uplink channel is NPUSCH and the uplink interval is used by the terminal device for TA adjustment in that uplink interval, this uplink interval is called the fourth uplink interval.

[0135] Optionally, the first, second, third, and fourth uplink intervals can be completely different, partially the same, or completely identical. For example, the first and second uplink intervals can be the same, and the third and fourth uplink intervals can be the same. Alternatively, the first and third uplink intervals can be the same, and the second and fourth uplink intervals can be the same. Or, the first, second, third, and fourth uplink intervals can all be different. Still another possibility is that the first, second, third, and fourth uplink intervals can all be the same. In short, this application does not impose any limitations in this regard.

[0136] Example 3

[0137] As mentioned above, in current LTE, considering the transition time between the transmitting and receiving operations of the terminal device, the terminal device initiates the Random Access Response (RAR) window after a certain interval following the transmission of Msg1. For NB-IoT terminals, the starting subframe of the RAR window is n+X, where n is the last subframe containing the last repeated transmission of the preamble, and the value of X is determined based on TDD or FDD and the number of NPRACH repeated transmissions. Specifically, the value of X can be determined using Table 1.

[0138] In Table 1, X = 41 is actually 40 + 1, where 40 represents the predefined uplink interval duration. As in this application, in non-GEO scenarios of the NTN network, the uplink interval is no longer predefined but configured by the network device. Based on this, the opening time of the random access response window will also change. This will be explained in detail below:

[0139] Optionally, assuming the insertion interval and duration of the first uplink interval are represented by X1 and Y1 respectively, the opening time of the random access response window can be n+Z1. n represents the last subframe used in the last retransmission of the preamble, and Z1 is determined by the total duration of the preamble retransmission, or the duration from the end time of the last first uplink interval inserted in the entire retransmission of the preamble to the end time of the entire retransmission of the preamble, and the RTT between the terminal device and the network device.

[0140] Optionally, assuming Z1 is determined by the total duration of repeated transmissions of the preamble, if the total duration of repeated transmissions of the preamble is greater than or equal to X1, then Z1 = max{Y1+1, RTT} or Z1 = max{Y1+1, RTT+1}. For example: Figure 6 This is a schematic diagram illustrating the relationship between the preamble, the first uplink interval, and the random access response window, provided in an embodiment of this application. Figure 6As shown, the total duration of repeated transmission of the preamble here is greater than X1. In this case, Z1 = max{Y1+1, RTT} or Z1 = max{Y1+1, RTT+1}.

[0141] If the total duration of repeated transmission of the preamble is less than X1, then Z1 = max{4, RTT} or Z1 = max{4, RTT+1}.

[0142] Optionally, Z1 is assumed to be determined by the duration from the end time of the last first uplink interval inserted in the entire repetition transmission of the preamble to the end time of the entire repetition transmission of the preamble, and the RTT between the terminal device and the network device. If the total repetition transmission duration of the preamble is equal to X1, then Z1 = max{Y1+1, RTT} or Z1 = max{Y1+1, RTT+1}. For example: Figure 7 A schematic diagram illustrating the relationship between the preamble, the first uplink interval, and the random access response window is provided in another embodiment of this application, as shown below. Figure 7 As shown, the total duration of the preamble repetition transmission is equal to X1. In this case, Z1 = max{Y1+1, RTT} or Z1 = max{Y1+1, RTT+1}. Alternatively, if the end time of the last first uplink interval inserted in the entire repetition transmission of the preamble is equal to the end time of the entire repetition transmission of the preamble, then Z1 = max{Y1+1, RTT} or Z1 = max{Y1+1, RTT+1}. For example: Figure 8 A schematic diagram illustrating the relationship between the preamble, the first uplink interval, and the random access response window is provided in another embodiment of this application, as shown below. Figure 8 As shown, here, if the end time of the last first uplink interval inserted in the entire repeated transmission of the preamble is equal to the end time of the entire repeated transmission of the preamble, then Z1 = max{Y1+1, RTT} or Z1 = max{Y1+1, RTT+1}. If the total duration of the repeated transmission of the preamble is less than X1, then Z1 = max{4, RTT} or Z1 = max{4, RTT+1}. Alternatively, if the end time of the last first uplink interval inserted in the entire repeated transmission of the preamble is less than X1, then Z1 = max{4, RTT} or Z1 = max{4, RTT+1}.

[0143] The above determines the opening time of the random access response window based on the first uplink interval.

[0144] In fact, in this application, the opening time of the random access response window can also be determined based on the second uplink interval. Of course, the opening time of the random access response window can only be determined based on the first uplink interval or the second uplink interval.

[0145] Optionally, the opening time of the random access response window is n+Z3. n represents the last subframe used in the last retransmission of the preamble, and Z3 is determined by the total duration of the retransmission of the preamble, or the duration from the end time of the last second uplink interval inserted in the entire retransmission of the preamble to the end time of the entire retransmission of the preamble, and the RTT between the terminal device and the network device.

[0146] Optionally, if the total duration of the preamble repetition transmission is greater than or equal to X3, then Z3 = max{Y3+1, RTT} or Z3 = max{Y3+1, RTT+1}. If the total duration of the preamble repetition transmission is less than X3, then Z3 = max{4, RTT} or Z3 = max{4, RTT+1}. Here, X3 represents the insertion interval of the second uplink interval, and Y3 represents the duration of the second uplink interval.

[0147] Optionally, if the total duration of the preamble repetition transmission is equal to X3, or if the time from the end of the last second uplink interval inserted in the entire repetition transmission of the preamble to the end of the entire repetition transmission of the preamble is equal to X3, then Z3 = max{Y3+1, RTT} or Z3 = max{Y3+1, RTT+1}. If the total duration of the preamble repetition transmission is less than X3, or if the time from the end of the last second uplink interval inserted in the entire repetition transmission of the preamble to the end of the entire repetition transmission of the preamble is less than X3, then Z3 = max{4, RTT} or Z3 = max{4, RTT+1}.

[0148] It is worth mentioning that the method for determining the opening time of the random access response window based on the second time interval is similar to the method for determining the opening time of the random access response window based on the first time interval, and will not be described in detail here.

[0149] In summary, this application provides a method for determining the opening time of the random access response window in a non-GEO scenario of an NTN network.

[0150] The above text combined Figures 4 to 8 The method embodiments of this application are described in detail below, in conjunction with... Figures 9 to 15 The present application describes the device embodiments in detail. It should be understood that the device embodiments correspond to the method embodiments, and similar descriptions can be referred to the method embodiments.

[0151] Figure 9 A schematic block diagram of a terminal device 900 according to an embodiment of this application is shown. Figure 9As shown, the terminal device 900 includes a communication unit 910, used for: acquiring uplink interval configuration information; and repeatedly transmitting uplink information on the uplink channel according to the uplink interval configuration information. The uplink interval is used by the terminal device for downlink synchronization and frequency offset compensation within the uplink interval.

[0152] Optionally, the configuration information for the uplink interval includes: the duration of the uplink interval, and / or, the insertion interval of the uplink interval. Specifically, an uplink interval occurs after each continuous insertion interval in the uplink channel.

[0153] Optionally, the uplink channel is NPRACH.

[0154] Optionally, the uplink interval is also used for terminal equipment to perform TA pre-compensation and / or downlink synchronization and frequency offset compensation on the uplink interval.

[0155] Optionally, the configuration information for the uplink interval is configuration information for at least one NPRACH.

[0156] Optionally, the uplink information is the preamble in the random access process. The terminal device further includes a processing unit 920, configured to open a random access response window after sending the preamble. The opening time of the random access response window is n+Z1. n represents the last subframe used in the last retransmission of the preamble, and Z1 is determined by the total duration of the retransmission of the preamble, or the duration from the end time of the last uplink interval inserted in the entire retransmission of the preamble to the end time of the entire retransmission of the preamble, and the RTT between the terminal device and the network device.

[0157] Optionally, if the total duration of the preamble repetition transmission is greater than or equal to X1, then Z1 = max{Y1+1, RTT} or Z1 = max{Y1+1, RTT+1}. If the total duration of the preamble repetition transmission is less than X1, then Z1 = max{4, RTT} or Z1 = max{4, RTT+1}. Here, X1 represents the insertion interval of the uplink interval, and Y1 represents the duration of the uplink interval.

[0158] Optionally, if the total duration of the preamble repetition transmission is equal to X1, or if the time from the end of the last uplink interval inserted in the entire repetition transmission of the preamble to the end of the entire repetition transmission of the preamble is equal to X1, then Z1 = max{Y1+1, RTT} or Z1 = max{Y1+1, RTT+1}. If the total duration of the preamble repetition transmission is less than X1, or if the time from the end of the last uplink interval inserted in the entire repetition transmission of the preamble to the end of the entire repetition transmission of the preamble is less than X1, then Z1 = max{4, RTT} or Z1 = max{4, RTT+1}. Where X1 represents the uplink interval insertion interval, and Y1 represents the duration of the uplink interval.

[0159] Optionally, the uplink channel is NPUSCH.

[0160] Optionally, the uplink interval is also used for terminal equipment to perform TA adjustment and / or downlink synchronization and frequency offset compensation on the uplink interval.

[0161] Optionally, the configuration information for the uplink interval is carried in any of the following: broadcast message, RRC signaling, MAC CE, or DCI.

[0162] Optionally, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip. The processing unit may be one or more processors.

[0163] It should be understood that the terminal device 900 according to the embodiments of this application may correspond to the terminal device in the method embodiments of this application, and the above and other operations and / or functions of each unit in the terminal device 900 are respectively to implement the corresponding process of the terminal device in the above method embodiments. For the sake of brevity, they will not be described in detail here.

[0164] Figure 10 A schematic block diagram of a terminal device 1000 according to an embodiment of this application is shown. Figure 10 As shown, the terminal device 1000 includes a communication unit 1010, configured to: acquire uplink interval configuration information; and repeatedly transmit uplink information on the uplink channel according to the uplink interval configuration information. The uplink interval is used by the terminal device to perform TA pre-compensation or TA adjustment within the uplink interval.

[0165] Optionally, the configuration information for the uplink interval includes: the duration of the uplink interval, and / or, the insertion interval of the uplink interval. Specifically, an uplink interval occurs after each continuous insertion interval in the uplink channel.

[0166] Optionally, the uplink channel is NPRACH.

[0167] Optionally, the uplink interval is used by the terminal equipment to perform TA pre-compensation and / or downlink synchronization and frequency offset compensation on the uplink interval.

[0168] Optionally, the configuration information for the uplink interval is configuration information for at least one NPRACH.

[0169] Optionally, the uplink information is the preamble in the random access process. The terminal device further includes a processing unit 1020, used to open a random access response window after sending the preamble. The opening time of the random access response window is n+Z3. n represents the last subframe used in the last repetition of the preamble, and Z3 is determined by the total duration of the repetition of the preamble, or the duration from the end time of the last uplink interval inserted in the entire repetition of the preamble to the end time of the entire repetition of the preamble, and the round-trip time (RTT) between the terminal device and the network device.

[0170] Optionally, if the total duration of the preamble repetition transmission is greater than or equal to X3, then Z3 = max{Y3+1, RTT} or Z3 = max{Y3+1, RTT+1}. If the total duration of the preamble repetition transmission is less than X3, then Z3 = max{4, RTT} or Z3 = max{4, RTT+1}. Here, X3 represents the insertion interval of the uplink interval, and Y3 represents the duration of the uplink interval.

[0171] Optionally, if the total duration of the preamble repetition transmission is equal to X3, or if the time from the end of the last uplink interval inserted in the entire repetition transmission of the preamble to the end of the entire repetition transmission of the preamble is equal to X3, then Z3 = max{Y3+1, RTT} or Z3 = max{Y3+1, RTT+1}. If the total duration of the preamble repetition transmission is less than X3, or if the time from the end of the last uplink interval inserted in the entire repetition transmission of the preamble to the end of the entire repetition transmission of the preamble is less than X3, then Z3 = max{4, RTT} or Z3 = max{4, RTT+1}. Here, X3 represents the uplink interval insertion interval, and Y3 represents the duration of the uplink interval.

[0172] Optionally, the uplink channel is NPUSCH.

[0173] Optionally, the uplink interval is also used for the terminal equipment to perform TA adjustment on the uplink interval.

[0174] Optionally, the configuration information for the uplink interval is carried in any of the following: broadcast message, RRC signaling, MAC CE, or DCI.

[0175] Optionally, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip. The processing unit may be one or more processors.

[0176] It should be understood that the terminal device 1000 according to the embodiments of this application may correspond to the terminal device in the method embodiments of this application, and the above and other operations and / or functions of each unit in the terminal device 1000 are respectively to implement the corresponding process of the terminal device in the above method embodiments. For the sake of brevity, they will not be described in detail here.

[0177] Figure 11 A schematic block diagram of a network device 1100 according to an embodiment of this application is shown. Figure 11 As shown, the network device 1100 includes a communication unit 1110 for transmitting uplink interval configuration information. The uplink interval is used by the terminal device for downlink synchronization and frequency offset compensation within the uplink interval.

[0178] Optionally, the configuration information for the uplink interval includes: the duration of the uplink interval, and / or, the insertion interval of the uplink interval. Specifically, an uplink interval occurs after each continuous insertion interval in the uplink channel.

[0179] Optionally, the uplink channel is NPRACH.

[0180] Optionally, the uplink interval is also used for terminal equipment to perform TA pre-compensation and / or downlink synchronization and frequency offset compensation on the uplink interval.

[0181] Optionally, the configuration information for the uplink interval is configuration information for at least one NPRACH.

[0182] Optionally, the uplink channel is NPUSCH.

[0183] Optionally, the uplink interval is also used for the terminal equipment to perform TA adjustment on the uplink interval.

[0184] Optionally, the configuration information for the uplink interval is carried in any of the following: broadcast message, RRC signaling, MAC CE, or DCI.

[0185] Optionally, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip.

[0186] It should be understood that the network device 1100 according to the embodiments of this application may correspond to the network device in the method embodiments of this application, and the above and other operations and / or functions of each unit in the network device 1100 are respectively to implement the corresponding process of the network device in the above method embodiments. For the sake of brevity, they will not be described in detail here.

[0187] Figure 12 A schematic block diagram of a network device 1200 according to an embodiment of this application is shown. Figure 12 As shown, the network device 1200 includes a communication unit 1210 for transmitting uplink interval configuration information. The uplink interval is used by the terminal device to perform TA pre-compensation or TA adjustment within the uplink interval.

[0188] Optionally, the configuration information for the uplink interval includes: the duration of the uplink interval, and / or, the insertion interval of the uplink interval. Specifically, an uplink interval occurs after each continuous insertion interval in the uplink channel.

[0189] Optionally, the uplink channel is NPRACH.

[0190] Optionally, the uplink interval is used by the terminal equipment to perform TA pre-compensation and / or downlink synchronization and frequency offset compensation on the uplink interval.

[0191] Optionally, the configuration information for the uplink interval is configuration information for at least one NPRACH.

[0192] Optionally, the uplink channel is NPUSCH.

[0193] Optionally, the uplink interval is also used for the terminal equipment to perform TA adjustment on the uplink interval.

[0194] Optionally, the configuration information for the uplink interval is carried in any of the following: broadcast message, RRC signaling, MAC CE, or DCI.

[0195] Optionally, in some embodiments, the communication unit may be a communication interface or transceiver, or an input / output interface of a communication chip or system-on-a-chip.

[0196] It should be understood that the network device 1200 according to the embodiments of this application may correspond to the network device in the method embodiments of this application, and the above and other operations and / or functions of each unit in the network device 1200 are respectively to implement the corresponding process of the network device in the above method embodiments. For the sake of brevity, they will not be described in detail here.

[0197] Figure 13 This is a schematic structural diagram of a communication device 1300 provided in an embodiment of this application. Figure 13 The communication device 1300 shown includes a processor 1310, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0198] Optionally, such as Figure 13As shown, the communication device 1300 may further include a memory 1320. The processor 1310 can retrieve and run computer programs from the memory 1320 to implement the methods described in this embodiment.

[0199] The memory 1320 can be a separate device independent of the processor 1310, or it can be integrated into the processor 1310.

[0200] Optionally, such as Figure 13 As shown, the communication device 1300 may also include a transceiver 1330, and the processor 1310 may control the transceiver 1330 to communicate with other devices. Specifically, it may send information or data to other devices or receive information or data sent by other devices.

[0201] The transceiver 1330 may include a transmitter and a receiver. The transceiver 1330 may further include an antenna, and the number of antennas may be one or more.

[0202] Optionally, the communication device 1300 may specifically be a network device in the embodiments of this application, and the communication device 1300 may implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0203] Optionally, the communication device 1300 may specifically be a terminal device in the embodiments of this application, and the communication device 1300 may implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0204] Figure 14 This is a schematic structural diagram of the device according to an embodiment of this application. Figure 14 The illustrated apparatus 1400 includes a processor 1410, which can call and run computer programs from memory to implement the methods in the embodiments of this application.

[0205] Optionally, such as Figure 14 As shown, the device 1400 may further include a memory 1420. The processor 1410 can retrieve and run computer programs from the memory 1420 to implement the methods described in the embodiments of this application.

[0206] The memory 1420 can be a separate device independent of the processor 1410, or it can be integrated into the processor 1410.

[0207] Optionally, the device 1400 may further include an input interface 1430. The processor 1410 can control the input interface 1430 to communicate with other devices or chips; specifically, it can acquire information or data sent by other devices or chips.

[0208] Optionally, the device 1400 may further include an output interface 1440. The processor 1410 can control the output interface 1440 to communicate with other devices or chips; specifically, it can output information or data to other devices or chips.

[0209] Optionally, the device can be applied to the network device in the embodiments of this application, and the device can implement the corresponding processes implemented by the network device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0210] Optionally, the device can be applied to the terminal device in the embodiments of this application, and the device can implement the corresponding processes implemented by the terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0211] Optionally, the device mentioned in the embodiments of this application can also be a chip. For example, it can be a system-on-a-chip, a system-on-a-chip, a chip system, or a system-on-a-chip, etc.

[0212] Figure 15 This is a schematic block diagram of a communication system 1500 provided in an embodiment of this application. Figure 15 As shown, the communication system 1500 includes a terminal device 1510 and a network device 1520.

[0213] The terminal device 1510 can be used to implement the corresponding functions implemented by the terminal device in the above method, and the network device 1520 can be used to implement the corresponding functions implemented by the network device or base station in the above method. For the sake of brevity, it will not be described in detail here.

[0214] It should be understood that the processor in the embodiments of this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. The storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0215] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0216] It should be understood that the above-described memory is exemplary and not a limiting description. For example, the memory in the embodiments of this application may also be static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct memory bus RAM (DR RAM), etc. That is to say, the memory in the embodiments of this application is intended to include, but is not limited to, these and any other suitable types of memory.

[0217] This application also provides a computer-readable storage medium for storing computer programs.

[0218] Optionally, the computer-readable storage medium can be applied to the network device or base station in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the network device or base station in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0219] Optionally, the computer-readable storage medium can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0220] This application also provides a computer program product, including computer program instructions.

[0221] Optionally, the computer program product can be applied to the network device or base station in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the network device or base station in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0222] Optionally, the computer program product can be applied to the mobile terminal / terminal device in the embodiments of this application, and the computer program instructions cause the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0223] This application also provides a computer program.

[0224] Optionally, the computer program can be applied to the network device or base station in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the network device or base station in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0225] Optionally, the computer program can be applied to the mobile terminal / terminal device in the embodiments of this application. When the computer program is run on a computer, it causes the computer to execute the corresponding processes implemented by the mobile terminal / terminal device in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

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

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

[0228] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

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

[0230] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0231] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

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

Claims

1. A wireless communication method, characterized in that, include: Obtain the configuration information for the uplink interval; Uplink information on the uplink channel is repeatedly transmitted according to the configuration information of the uplink interval; The uplink interval is used by the terminal device to perform TA pre-compensation on the uplink interval; The uplink channel is NPRACH, and the uplink information is the preamble in the random access process; The method further includes: After sending the preamble, open the random access response window; Wherein, the opening time of the random access response window is n+Z3; n represents the last subframe used in the last retransmission of the preamble, and Z3 is determined by the total duration of the retransmission of the preamble and the RTT between the terminal device and the network device, or, Z3 is determined by the duration from the end time of the last uplink interval inserted in the entire retransmission of the preamble to the end time of the entire retransmission of the preamble and the RTT between the terminal device and the network device.

2. The method according to claim 1, characterized in that, The configuration information of the uplink interval includes: the duration of the uplink interval, and / or the insertion interval of the uplink interval; The uplink channel is followed by an uplink interval after each insertion interval.

3. The method according to claim 1 or 2, characterized in that, The configuration information for the uplink interval is configuration information for at least one NPRACH.

4. The method according to claim 1, characterized in that, If the total duration of repeated transmission of the preamble is greater than or equal to X3, then Z3 = max{Y3+1, RTT} or Z3 = max{Y3+1, RTT+1}. If the total duration of repeated transmission of the preamble is less than X3, then Z3 = max{4, RTT} or Z3 = max{4, RTT+1}. Wherein, X3 represents the insertion interval of the uplink interval, and Y3 represents the duration of the uplink interval.

5. The method according to claim 1, characterized in that, If the total duration of the repeated transmission of the preamble is equal to X3, or if the end time of the last uplink interval inserted in the entire repeated transmission of the preamble is equal to X3, then Z3 = max{Y3+1, RTT} or Z3 = max{Y3+1, RTT+1}. If the total duration of the repeated transmission of the preamble is less than X3, or if the end time of the last uplink interval inserted in the entire repeated transmission of the preamble is less than X3, then Z3 = max{4, RTT} or Z3 = max{4, RTT+1}. Wherein, X3 represents the insertion interval of the uplink interval, and Y3 represents the duration of the uplink interval.

6. The method according to claim 1 or 2, characterized in that, The uplink channel is NPUSCH.

7. The method according to claim 6, characterized in that, The uplink interval is also used by the terminal device to perform TA adjustment within the uplink interval.

8. The method according to any one of claims 1-7, characterized in that, The configuration information for the uplink interval is carried in any of the following: broadcast message, RRC signaling, MAC CE, or DCI.

9. A terminal device, characterized in that, include: Communication unit, used for: Obtain the configuration information for the uplink interval; Uplink information on the uplink channel is repeatedly transmitted according to the configuration information of the uplink interval; The uplink interval is used by the terminal device to perform TA pre-compensation on the uplink interval; The uplink channel is NPRACH, and the uplink information is the preamble in the random access process; The terminal device further includes a processing unit for: After sending the preamble, open the random access response window; Wherein, the opening time of the random access response window is n+Z3; n represents the last subframe used in the last retransmission of the preamble, and Z3 is determined by the total duration of the retransmission of the preamble and the RTT between the terminal device and the network device, or, Z3 is determined by the duration from the end time of the last uplink interval inserted in the entire retransmission of the preamble to the end time of the entire retransmission of the preamble and the RTT between the terminal device and the network device.

10. The terminal device according to claim 9, characterized in that, The configuration information of the uplink interval includes: the duration of the uplink interval, and / or the insertion interval of the uplink interval; The uplink channel is followed by an uplink interval after each insertion interval.

11. The terminal device according to claim 9 or 10, characterized in that, The configuration information for the uplink interval is configuration information for at least one NPRACH.

12. The terminal device according to claim 9, characterized in that, If the total duration of repeated transmission of the preamble is greater than or equal to X3, then Z3 = max{Y3+1, RTT} or Z3 = max{Y3+1, RTT+1}. If the total duration of repeated transmission of the preamble is less than X3, then Z3 = max{4, RTT} or Z3 = max{4, RTT+1}. Wherein, X3 represents the insertion interval of the uplink interval, and Y3 represents the duration of the uplink interval.

13. The terminal device according to claim 9, characterized in that, If the total duration of the repeated transmission of the preamble is equal to X3, or if the end time of the last uplink interval inserted in the entire repeated transmission of the preamble is equal to X3, then Z3 = max{Y3+1, RTT} or Z3 = max{Y3+1, RTT+1}. If the total duration of the repeated transmission of the preamble is less than X3, or if the end time of the last uplink interval inserted in the entire repeated transmission of the preamble is less than X3, then Z3 = max{4, RTT} or Z3 = max{4, RTT+1}. Wherein, X3 represents the insertion interval of the uplink interval, and Y3 represents the duration of the uplink interval.

14. The terminal device according to claim 9 or 10, characterized in that, The uplink channel is NPUSCH.

15. The terminal device according to claim 14, characterized in that, The uplink interval is also used by the terminal device to perform TA adjustment within the uplink interval.

16. The terminal device according to any one of claims 9-15, characterized in that, The configuration information for the uplink interval is carried in any of the following: broadcast message, RRC signaling, MAC CE, or DCI.

17. A terminal device, characterized in that, include: A processor and a memory, the memory being used to store a computer program, the processor being used to invoke and run the computer program stored in the memory to perform the method as described in any one of claims 1 to 8.

18. An apparatus, characterized in that, include: A processor for retrieving and running a computer program from memory, causing a device equipped with the means to perform the method as described in any one of claims 1 to 8.

19. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform the method as described in any one of claims 1 to 8.

20. A computer program product, characterized in that, It includes computer program instructions that cause a computer to perform the method as described in any one of claims 1 to 8.

Images