Wireless communication method and apparatus, device, chip, and storage medium

Abstract

A wireless communication method and apparatus, a device, a chip, and a storage medium, relating to the technical field of communications. The method comprises: a terminal device sends a first message (step 610); and the terminal device calculates a first RNTI on the basis of a time-frequency resource used by the first message (step 620). The terminal device is a terminal device in an NTN TDD system. In the method, for the NTN TDD system, the first RNTI can be accurately calculated on the basis of the time-frequency resource used by the first message. It is convenient for the terminal device to subsequently monitor a PDCCH associated with the first RNTI, thereby determining a reception status of the first message.

Description

Wireless communication methods, devices, equipment, chips and storage media Technical Field

[0001] This application relates to the field of communication technology, and in particular to a wireless communication method, apparatus, device, chip, and storage medium. Background Technology

[0002] NTN (Non-Terrestrial Networks) and TDD (Time Division Duplex) systems refer to wireless communication systems based on non-terrestrial platforms. Uplink and downlink transmission are achieved by dividing time into multiple independent time slots, each of which can be dedicated to either uplink or downlink transmission.

[0003] The introduction of TDD mode will lead to discontinuous uplink and downlink transmission, and it is necessary to study the impact of this transmission mode on the terminal device's behavior of listening to PDCCH (Physical Downlink Control Channel). Summary of the Invention

[0004] This application provides a wireless communication method, apparatus, device, chip, and storage medium. The technical solutions provided by this application are as follows.

[0005] According to one aspect of the embodiments of this application, a wireless communication method is provided, the method being executed by a terminal device in an NTN TDD system, the method comprising:

[0006] Send the first message;

[0007] Based on the time-frequency resources used by the first message, calculate the first RNTI (Radio Network Temporary Identifier).

[0008] According to one aspect of the embodiments of this application, a wireless communication method is provided, the method being performed by a network device in an NTN TDD system, the method comprising:

[0009] Receive the first message;

[0010] Calculate the first RNTI based on the time-frequency resources used by the first message.

[0011] According to one aspect of the embodiments of this application, a wireless communication method is provided, the method being executed by a terminal device in an NTN TDD system, the method comprising:

[0012] On the available downlink time domain units within the time interval of the first channel or signal transmission, the PDCCH is not monitored.

[0013] According to one aspect of the embodiments of this application, a wireless communication method is provided, the method being performed by a network device in an NTN TDD system, the method comprising:

[0014] No PDCCH is transmitted on the available downlink time domain units within the time interval of the first channel or signal transmission.

[0015] According to one aspect of the embodiments of this application, a wireless communication device is provided, the device comprising: a transmitting module and a processing module;

[0016] The sending module is used to send the first message;

[0017] The processing module is used to calculate the first RNTI based on the time-frequency resources used by the first message.

[0018] According to one aspect of the embodiments of this application, a wireless communication device is provided, the device comprising: a receiving module and a processing module;

[0019] The receiving module is used to receive the first message;

[0020] The processing module is used to calculate the first RNTI based on the time-frequency resources used by the first message.

[0021] According to one aspect of the embodiments of this application, a wireless communication device is provided, the device comprising: a receiving module;

[0022] The receiving module is configured not to listen to the PDCCH on the available downlink time domain units within the time interval of the first channel or signal transmission.

[0023] According to one aspect of the embodiments of this application, a wireless communication device is provided, the device comprising: a transmitting module;

[0024] The transmitting module is configured not to transmit PDCCH on available downlink time domain units within the time interval of the first channel or signal transmission.

[0025] According to one aspect of the embodiments of this application, a communication device is provided, the communication device including a processor and a memory, the memory storing a computer program, and the processor executing the computer program to implement the above-described wireless communication method.

[0026] According to one aspect of the embodiments of this application, a computer-readable storage medium is provided, wherein the storage medium stores a computer program for execution by a processor to implement the above-described wireless communication method.

[0027] According to one aspect of the embodiments of this application, a chip is provided, the chip including programmable logic circuits and / or program instructions, which, when the chip is running, are used to implement the above-described wireless communication method.

[0028] According to one aspect of the embodiments of this application, a computer program product is provided, the computer program product including computer instructions stored in a computer-readable storage medium, and a processor reading from the computer-readable storage medium and executing the computer instructions to implement the above-described wireless communication method.

[0029] The technical solutions provided in this application embodiment may have the following beneficial effects:

[0030] For NTN TDD systems, the first RNTI can be accurately calculated based on the time-frequency resources used by the first message. This facilitates the terminal device's subsequent monitoring of the PDCCH associated with the first RNTI, thereby determining the reception status of the first message. Attached Figure Description

[0031] Figure 1 is a schematic diagram of a network architecture provided in one embodiment of this application;

[0032] Figure 2 is a schematic diagram of a contention-based random access method provided in an embodiment of this application;

[0033] Figure 3 is a schematic diagram of a non-contention-based random access method provided in an embodiment of this application;

[0034] Figure 4 is a schematic diagram of a DRX cycle provided in an embodiment of this application;

[0035] Figure 5 is a schematic diagram of a TDD mode frame structure provided in an embodiment of this application;

[0036] Figure 6 is a flowchart of a wireless communication method provided in an embodiment of this application;

[0037] Figure 7 is a flowchart of a wireless communication method provided in another embodiment of this application;

[0038] Figure 8 is a schematic diagram of two TDD frames provided in an embodiment of this application;

[0039] Figure 9 is a block diagram of a wireless communication device provided in an embodiment of this application;

[0040] Figure 10 is a block diagram of a wireless communication device provided in another embodiment of this application;

[0041] Figure 11 is a block diagram of a wireless communication device provided in another embodiment of this application;

[0042] Figure 12 is a block diagram of a wireless communication device provided in another embodiment of this application;

[0043] Figure 13 is a schematic diagram of the structure of a communication device provided in an embodiment of this application. Detailed Implementation

[0044] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described in further detail below with reference to the accompanying drawings.

[0045] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0046] The technical solutions of this application embodiment can be applied to various communication systems, such as: Global System for Mobile communication (GSM) system, Code Division Multiple Access (CDMA) system, Wideband Code Division Multiple Access (WCDMA) system, General Packet Radio Service (GPRS), Long Term Evolution (LTE) system, Advanced Long Term Evolution (LTE-A) system, New Radio System, evolution system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), and Wireless Fidelity (WF). Fidelity (WiFi), 5th-Generation (5G) systems, B5G (Beyond 5G) systems, 6th-Generation (6G) systems, or other communication systems.

[0047] Traditional communication systems typically support a limited number of connections and are easy to implement. However, with the development of communication technology, mobile communication systems will not only support traditional communication but also, for example, device-to-device (D2D) communication, machine-to-machine (M2M) communication, machine-type communication (MTC), vehicle-to-vehicle (V2V) communication, or vehicle-to-everything (V2X) communication. The embodiments of this application can also be applied to these communication systems.

[0048] The communication system in this application embodiment can be applied to carrier aggregation scenarios, dual connectivity (DC) scenarios, and standalone (SA) network deployment scenarios.

[0049] The communication system in this application embodiment can be applied to unlicensed spectrum, wherein unlicensed spectrum can also be considered as shared spectrum; or, the communication system in this application embodiment can also be applied to licensed spectrum, wherein licensed spectrum can also be considered as non-shared spectrum.

[0050] The embodiments of this application can be applied to both non-terrestrial networks (NTN) and terrestrial networks (TN). NTN typically uses satellite communication to provide communication services to terrestrial users. Currently, NTN systems include NR-NTN and IoT-NTN systems, and other NTN systems may be included in the future.

[0051] Please refer to Figure 1, which shows a schematic diagram of a network architecture 100 provided in one embodiment of this application. The network architecture 100 may include: a terminal device 10, an access network device 20, and a core network element 30.

[0052] Terminal device 10 can refer to UE (User Equipment), access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, wireless communication device, user agent, or user equipment. In some embodiments, terminal device 10 can also be a cellular phone, cordless phone, SIP (Session Initiation Protocol) phone, WLL (Wireless Local Loop) station, PDA (Personal Digital Assistant), handheld device with wireless communication capabilities, computing device or other processing device connected to a wireless modem, vehicle-mounted device, wearable device, terminal device in 5GS (5th Generation System), or terminal device in the future evolved PLMN (Public Land Mobile Network), etc., and this application embodiment is not limited thereto. For ease of description, the devices mentioned above are collectively referred to as terminal devices. The number of terminal devices 10 is usually multiple, and one or more terminal devices 10 can be distributed within the cell managed by each access network device 20. Terminal equipment can also be simply referred to as terminal or UE, the meaning of which can be understood by those skilled in the art.

[0053] Access network device 20 is a device deployed in an access network to provide wireless communication functionality to terminal device 10. Access network device 20 may include various forms of macro base stations, micro base stations, relay stations, access points, etc. In systems employing different wireless access technologies, the name of the device with access network device functionality may differ; for example, in a 5G NR system, it is called gNodeB or gNB. As communication technologies evolve, the name "access network device" may change. For ease of description, in this embodiment, the aforementioned devices providing wireless communication functionality to terminal device 10 are collectively referred to as access network devices. In some embodiments, a communication relationship can be established between terminal device 10 and core network element 30 through access network device 20. For example, in an LTE (Long Term Evolution) system, access network device 20 may be one or more eNodeBs in an EUTRAN (Evolved Universal Terrestrial Radio Access Network) or EUTRAN; in a 5G NR system, access network device 20 may be one or more gNBs in a RAN (Radio Access Network). In the embodiments of this application, unless otherwise specified, the term "network device" refers to access network device 20, such as a base station.

[0054] Core network element 30 is a network element deployed in the core network. Its main functions are to provide user connectivity, manage users, and bear services, serving as an interface to external networks. For example, core network elements in a 5G NR system may include AMF (Access and Mobility Management Function) entities, UPF (User Plane Function) entities, and SMF (Session Management Function) entities.

[0055] In some embodiments, the access network device 20 and the core network element 30 communicate with each other via some air interface technology, such as the NG interface in a 5G NR system. The access network device 20 and the terminal device 10 communicate with each other via some air interface technology, such as the Uu interface.

[0056] The "5G NR system" in this application embodiment can also be referred to as a 5G system or an NR system, but those skilled in the art will understand its meaning. The technical solutions described in this application embodiment can be applied to LTE systems, 5G NR systems, and subsequent evolution systems of 5G NR systems (such as B5G (Beyond 5G, a fifth-generation mobile communication technology) systems, 6G systems (6th Generation System, a sixth-generation mobile communication system)), and other communication systems such as NB-IoT (Narrow Band Internet of Things) systems. This application does not limit these applications.

[0057] 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) on the carrier 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.

[0058] Before introducing the technical solution of this application, some related technical knowledge involved in this application will be introduced and explained. The following related technologies are optional solutions and can be arbitrarily combined with the technical solutions of the embodiments of this application, all of which fall within the protection scope of the embodiments of this application. The embodiments of this application include at least some of the following contents.

[0059] 1. Background information on NTN

[0060] Currently, 3GPP is researching NTN technology, which generally 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 the user's geographical location. For example, conventional terrestrial communication cannot cover areas such as oceans, mountains, and deserts where communication equipment cannot be built or where there is no communication coverage due to sparse population. However, for satellite communication, since a single satellite can cover a large area, and satellites can 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 of communication does not increase significantly with the increase in communication distance. Finally, satellite communication has high stability and is not affected by natural disasters.

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

[0062] 1. LEO

[0063] 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.

[0064] 2. GEO

[0065] 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.

[0066] 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.

[0067] 2. LTE Random Access Procedure

[0068] In LTE, the random access process is mainly triggered by the following events:

[0069] 1. Establishing a radio connection during initial UE access: The UE transitions from the RRC (Radio Resource Control)_IDLE state (idle state) to the RRC_CONNECTED state (connected state);

[0070] 2. RRC connection reconstruction process: to enable the UE to rebuild the radio connection after the radio link fails;

[0071] 3. Handover: The UE needs to establish uplink synchronization with the new cell;

[0072] 4. In the RRC_CONNECTED state, DL (DownLink) data arrives, and UL is out of sync at this time;

[0073] 5. In the RRC_CONNECTED state, UL (UpLink) data arrives. At this time, the UL is out of sync or does not have PUCCH resources for sending SR (Scheduling Request).

[0074] 6. SR failed;

[0075] 7. Synchronous reconfiguration request from RRC.

[0076] In LTE, two main random access methods are supported: contention-based random access and contention-free random access. These two methods are applicable to different scenarios. In contention-based random access, the RACH (Random Access Channel) is a resource pool available to the terminal device, and different terminal devices can use the same resources, leading to resource contention. In contention-free random access, specific resources are reserved and allocated to a specific terminal device at a given time.

[0077] Figure 2 illustrates a contention-based random access method, characterized by code resource sharing and a four-step access process, including access request, access response, connection request, and contention resolution (also known as conflict resolution). This process comprises steps Step 1 through Step 4. It is important to note that the interaction messages in each step of the contention-based random access method are referred to as Msg1 through Msg4.

[0078] Step 1: Access Request (Msg1)

[0079] The terminal device selects a PRACH (Physical Random Access Channel) resource (including time-frequency resources and code domain resources) and transmits the selected preamble on the selected PRACH time-frequency resource. Based on the preamble, the network device can estimate the uplink timing and the grant size required for the terminal device to transmit Msg3.

[0080] Step 2: Access Response (Msg2)

[0081] After receiving the preamble from the terminal device, the network device sends a RAR (Random Access Response) to the terminal device. After sending Msg1, the terminal device opens a RAR window and monitors the PDCCH (Physical Downlink Control Channel) scrambled with RA-RNTI (Random Access-Radio Network Temporary Identifier).

[0082] In LTE systems, RA-RNTI is calculated as follows:

[0083] RA-RNTI = 1 + t_id + 10 * f_id

[0084] Where t_id is the index of the first subframe of PRACH transmission (0≤t_id<10), and f_id is the frequency domain index of the corresponding PRACH in that subframe (0≤f_id<6). The PRACH resources are numbered sequentially in the frequency domain from low to high.

[0085] For an eMTC (enhanced Machine-Type Communication) UE, the RA-RNTI is calculated as follows: RA-RNTI = 1 + t_id + 10 * f_id + 60 * (SFN_id mod (Wmax / 10))

[0086] Where mod is the modulo operation, t_id is the index of the first subframe of PRACH transmission (0≤t_id<10), f_id is the frequency domain index of the corresponding PRACH in that subframe (0≤f_id<6), and PRACH resources are numbered sequentially in the frequency domain from low to high. SFN_id is the index of the first SFN (system frame) of PRACH transmission, and Wmax is the maximum RAR window length supported by eMTC, which is 400 subframes.

[0087] For NB-IoT UEs, the RA-RNTI is calculated as follows: RA-RNTI = 1 + floor(SFN_id / 4) + 256 * carrier_id

[0088] Where floor is calculated by rounding up, SFN_id is the index of the first SFN in the PRACH transmission, and carrier_id is the index of the UL carrier corresponding to the PRACH transmission. The carrier_id for the Anchor carrier is 0.

[0089] For NB-IoT UEs in TDD (Time Division Duplexing) mode, the RA-RNTI is calculated as follows: RA-RNTI = 1 + floor(SFN_id / 4) + 256*(H-SFN mod 2)

[0090] Wherein, SFN_id is the index of the first SFN transmitted by PRACH, and H-SFN is the index of the first H-SFN (superframe) transmitted by PRACH.

[0091] As can be seen from the calculation formula of RA-RNTI above, RA-RNTI is related to the PRACH time and frequency resources used by the terminal device to send Msg1.

[0092] After the terminal device successfully receives the RA-RNTI scrambled PDCCH, it can obtain the PDSCH (Physical Downlink Shared Channel) scheduled by the PDCCH, which contains RAR.

[0093] The RAR subheader contains a BI (Backoff Indicator), which indicates the backoff time for retransmitting Msg1.

[0094] RAPID (Random Access Preamble ID) in RAR: the preamble index received in the network response;

[0095] The payload in the RAR contains a TAG, which is used to adjust the uplink timing;

[0096] The UL grant (uplink grant) in the RAR message indicates the uplink resources used to schedule Msg3. Because the terminal device has not yet established an RRC connection with the network device or performed uplink synchronization, it cannot request uplink grants from the network device for uplink transmission via a Scheduling Request (SR). Instead, it must include uplink grant information in the RAR message to allow the terminal device to send the first uplink message, Msg3, which is the RRC Setup Request (RRC Connection Establishment Request). The UL-Grant field indicates the resources used for uplink transmission. The UL-Grant field is 20 bits long, and Msg3 is actually sent using these resources.

[0097] The Temporary C-RNTI in RAR, or TC-RNTI (Temporary Cell-RNTI, Temporary Cell-Radio Network Temporary Identifier), is used to scramble Msg4's PDCCH.

[0098] If the terminal device receives a PDCCH scrambled with RAR-RNTI, and the RAR contains the preamble index it sent, then the terminal considers it to have successfully received the random access response.

[0099] For non-contention-based random access, the random access process ends after the terminal successfully receives Msg2. For contention-based random access, after the terminal device successfully receives Msg2, it still needs to transmit Msg3 and receive Msg4.

[0100] Step 3: Connection Request (Msg3)

[0101] Msg3 is primarily used to inform network devices what event triggered the RACH procedure. For example, if it's an initial access random procedure, Msg3 will carry the UE ID and establishment cause; if it's an RRC reconstruction, it will carry the connected UE identifier and establishment cause. Additionally, the ID carried in Msg3 allows contention to be resolved in Step 4.

[0102] Step 4: Competition Resolution (Msg4)

[0103] Msg4 has two functions: first, it is used for contention resolution, and second, it is used to transmit RRC configuration messages to the terminal device.

[0104] There are two ways to resolve contention: Method 1: If the terminal device carries a C-RNTI in Msg3, then Msg4 is scheduled using a PDCCH scrambled with the C-RNTI. Method 2: If the terminal device does not carry a C-RNTI in Msg3, such as during initial access, then Msg4 is scheduled using a PDCCH scrambled with the TC-RNTI. Conflict resolution is achieved by the terminal device receiving the PDSCH carrying Msg4 and matching the CCCH (Common Control Channel) SDU (Service Data Unit) in the PDSCH with the contention resolution ID in its own Msg3.

[0105] Figure 3 illustrates a non-contention-based random access method, characterized by exclusive code resources and a three-step access process: preamble allocation, access request, and access response. This process includes the following steps: Step 0 to Step 2. It's important to note that the interaction messages in each step of this non-contention-based random access method are referred to as Msg0 to Msg2, respectively.

[0106] Step 0: Leader assignment (Msg0)

[0107] Network devices assign random access preambles to terminal devices and send them using RRC messages or DCI (Downlink Control Information).

[0108] Step 1: Access Request (Msg1)

[0109] Step 2: Access Response (Msg2)

[0110] For explanations of Msg1 and Msg2, please refer to the above text; they will not be repeated here.

[0111] As can be seen from the above random access process, the main purpose of random access is for the terminal device to achieve uplink synchronization with the cell. During the random access process, the network device can know the time when the terminal device sends the preamble based on the RACH time-frequency resources used by the preamble received from the terminal device. Therefore, it determines the initial TA (Timing Advance) of the terminal device based on the transmission and reception times of the preamble, and informs the terminal through the RAR.

[0112] 3. CB-Msg3 based EDT (Contention Based-Msg3 Early Data Transmission)

[0113] To reduce uplink and downlink signaling overhead and improve system uplink capacity, IoT NTN plans to further enhance EDT features, such as introducing RACH-less EDT, i.e., direct transmission of Msg3, which transmits Msg3 directly without going through the Msg1 / Msg2 process. The research objectives for this feature are as follows: Study and specify, if beneficial, the following enhancements to reduce the necessary uplink and downlink signaling to complete an EDT transaction [RAN2]: Msg3 transmission without msg1 / RAR; Efficient delivery (reduced overhead) of msg4 / RRC early Data Complete.

[0114] In traditional EDT, the base station allocates PUSCH resources for the initial transmission of Msg3 to the UE via Msg2. In traditional PUR (Preconfigured Uplink Resources), the base station provides PUR configuration information to the UE via an RRC connection release message when releasing the UE to the RRC IDLE state. Regarding PUSCH resources for Msg3 transmission in RACH-less EDT, the following conclusions have been reached: RAN2 focuses on contention-based Msg3 transmission to complete an EDT-like transaction (FFS on the details of Msg3, FFS on the procedural steps, e.g., how much we reuse of EDT and PUR procedures, FFS on resource allocation).

[0115] Based on current research progress, in CB-Msg3 based EDT, the base station configures the Msg3 resource for CB-Msg3 based EDT via system broadcast, and this Msg3 PUSCH is a shared resource. If multiple UEs select the same PUSCH resource to transmit Msg3 (i.e., multiple UEs experience Msg3 conflict), a conflict resolution mechanism informs the UE that successfully contested the resource. During this process, after the UE transmits Msg3, the RNTI used to listen to the PDCCH and Msg4 PDSCH is determined based on the resource used by the Msg3 PUSCH.

[0116] 4. LTE DRX (Discontinuous Reception) process

[0117] In LTE, the network can configure DRX functionality for terminals, enabling them to listen to the PDCCH discontinuously to save power. Each MAC (Media Access Control) entity has a DRX configuration, and the DRX configuration parameters include:

[0118] DRX cycle: DRX cycle;

[0119] drx-onDurationTimer: DRX continuous timer;

[0120] drx-StartOffset: The delay at which the UE starts drx-onDurationTimer;

[0121] drx-InactivityTimer: DRX inactivity timer;

[0122] drx-RetransmissionTimerDL: DRX downlink retransmission timer. Each downlink HARQ process, except for the broadcast HARQ (Hybrid Automatic Repeat reQuest) process, corresponds to one drx-RetransmissionTimerDL.

[0123] drx-RetransmissionTimerUL: DRX uplink retransmission timer. One drx-RetransmissionTimerUL corresponds to each uplink HARQ process.

[0124] If the terminal is configured with DRX, the terminal needs to listen to the PDCCH during the DRX activation period. The DRX activation period includes the following situations:

[0125] 1. Any one of the following seven timers is running: drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-DLRetransmissionTimerShortTTI (DRX Downlink Short Transmission Time Unit Retransmission Timer), drx-RetransmissionTimerUL, drx-ULRetransmissionTimerShortTTI (DRX Uplink Short Transmission Time Unit Retransmission Timer), and mac-ContentionResolutionTimer (MAC Contention Resolution Timer).

[0126] 2. An SR was sent on PUCCH / SPUCCH and is in a pending state.

[0127] 3. In a contention-based random access process, the terminal has not yet received the PDCCH indication scrambled by C-RNTI after successfully receiving the random access response during an initial transmission.

[0128] 4. A pending HARQ retransmission can receive a UL grant, and the asynchronous HARQ process must have data in its HARQ buffer.

[0129] 5. mpdcch-UL-HARQ-ACK-FeedbackConfig is configured and a recurring transfer within a bundle is currently in progress.

[0130] As shown in Figure 4, the terminal determines when to start the drx-onDurationTimer based on whether it is currently in a short DRX cycle or a long DRX cycle, as specified below:

[0131] 1. If the Short DRX Cycle is used, and the current subframe satisfies [(SFN×10)+subframe number]modulo(drx-ShortCycle)=(drxStartOffset)modulo(drx-ShortCycle); or

[0132] 2. If Long DRX Cycle is used, and the current subframe satisfies [(SFN×10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset;

[0133] (1) If it is NB-IoT, then: if at least one HARQ process has a corresponding HARQ RTT Timer (HARQ Round Trip Time Timer) or UL HARQ RTT Timer that is not running, then start drx-onDurationTimer.

[0134] (2) Otherwise, start drx-onDurationTimer.

[0135] The conditions for starting or restarting the HARQ RTT Timer in the terminal are:

[0136] If the terminal receives a PDCCH indicating downlink transmission, or if the terminal has a configured downlink grant in this subframe, then:

[0137] a) If the UE is an NB-IoT terminal or an eMTC terminal, then:

[0138] a1) If the PDCCH indicates that multiple TB (Transport Block) transmissions are scheduled, the UE starts the HARQ RTT Timer corresponding to all downlink HARQ processes used by the multiple TBs in the subframe where the last repeated transmission of the PDSCH of the last TB of the multiple TBs is received.

[0139] a2) Otherwise, the UE starts the HARQ RTT Timer corresponding to the downlink HARQ process used by the PDSCH in the subframe where the last repeated transmission of the PDSCH is received.

[0140] b) Otherwise, start the HARQ RTT Timer corresponding to the downlink HARQ process used by this PDSCH.

[0141] If the HARQ RTT Timer times out, then if the data decoding of the HARQ process fails, the UE will start the drx-RetransmissionTimerDL corresponding to the downlink HARQ process.

[0142] In addition, if the HARQ RTT Timer times out, for NB-IoT terminals: if the PDCCH indicates that multiple TBs are scheduled, then when the HARQ RTT Timer corresponding to the HARQ process used by all these TBs times out, drx-InactivityTimer is started or restarted; otherwise, drx-InactivityTimer is started or restarted.

[0143] The conditions for the terminal to start or restart the UL HARQ RTT Timer are:

[0144] If the terminal receives a PDCCH indicating an uplink transmission using an asynchronous HARQ process, or if the terminal has configured uplink grants for an asynchronous HARQ process in this subframe, or if the terminal receives a PDCCH indicating an uplink transmission using an automatic HARQ process, then:

[0145] a) If mpdcch-UL-HARQ-ACK-FeedbackConfig is not configured

[0146] a1) If the PDCCH indicates that multiple TB transmissions have been scheduled, the UE starts the UL HARQ RTT Timer corresponding to all uplink HARQ processes used by the PUSCH in the multiple TBs in the subframe where the last repeated transmission of the PUSCH of the last TB of the multiple TBs is located.

[0147] a2) Otherwise, the UE starts the UL HARQ RTT Timer corresponding to the uplink HARQ process used by the PUSCH in the subframe where the last repeated transmission of the PUSCH is completed.

[0148] If the UL HARQ RTT Timer corresponding to a certain uplink HARQ process times out, the UE starts the drx-RetransmissionTimerUL corresponding to that uplink HARQ process.

[0149] In addition, if the UL HARQ RTT Timer corresponding to a certain uplink HARQ process times out, for NB-IoT terminals: if the PDCCH indicates that multiple TBs are scheduled, then when the UL HARQ RTT Timer corresponding to the HARQ process used by all these TBs times out, drx-InactivityTimer is started or restarted; otherwise, drx-InactivityTimer is started or restarted.

[0150] 5. IoT NTN TDD mode

[0151] To enable IoT NTN to support a wider range of application scenarios, the 3GPP RAN plenary meeting agreed to make supporting NB-IoT FDD UEs operating in NGEO (Near GEO) systems at the 1616-1626.5MHz frequency range a new research and standardization goal. Currently, the 1616-1626.5MHz NTN frequency range is the operating frequency of Iridium satellites, operating in TDD mode, with the corresponding frame structure shown in Figure 5. This characteristic requires that NB-IoT FDD (Frequency Division Duplexing) UEs operating at this frequency range can coexist with the current Iridium TDD mode. Therefore, the new NB-IoT NTN TDD mode ensures that the NB-IoT system has only D consecutively available downlink subframes and U consecutively available uplink subframes within every N radio frames.

[0152] Based on the RAN plenary meeting discussion, it was decided that N=9 and D=U=8. Meanwhile, after two meetings, RAN1 reached the following conclusion: When the NB-IoT FDD UE operates in the 1.6GHz MSS band, the standardized design must consider the following limitations:

[0153] 1. On the satellite side, all NB-IoT downlink channels / signals within the cell can only use one downlink time slot in the 90ms period TDD frame structure, namely DL1, DL2, DL3, and DL4. Furthermore, the downlink time slot with the same number is used in all 90ms periods.

[0154] 2. On the satellite side, all NB-IoT uplink channels / signals within the cell can only use one uplink time slot in the 90ms period TDD frame structure, namely UL1, UL2, UL3, and UL4. Furthermore, the same uplink time slot number is used for all 90ms.

[0155] 3. In the TDD frame structure, the downlink and uplink time slots available to the NB-IoT FDD UE correspond to the same number, namely DL1&UL1, DL2&UL2, DL3&UL3, or DL4&UL4.

[0156] Based on the current meeting conclusions, when operating in the 1.6GHz MSS band, all downlink transmissions in an NB-IoT cell can only periodically use 8 consecutive downlink subframes within 90ms, and all uplink transmissions can only periodically use 8 consecutive uplink subframes within 90ms. To adapt to the new TDD frame structure, an intuitive enhancement is to change the configuration period of all periodic channels / signals to an integer multiple of 90ms. For the random access procedure, the following issues need to be addressed: First, the existing RA-RNTI calculation method leads to excessive RA-RNTI space consumption, meaning RA-RNTI values ​​are discontinuous and fragmented. Second, the start times of the RAR window and mac-ContentionResolutionTimer may not be located on available downlink subframes, causing the UE to start these timers prematurely. Furthermore, uplink and downlink transmissions in non-TDD systems are temporally continuous; the introduction of TDD mode will lead to discontinuous uplink and downlink transmissions, requiring research into the impact of this transmission method on UE PDCCH listening behavior (and the DRX process).

[0157] Please refer to Figure 6, which shows a flowchart of a wireless communication method provided in one embodiment of this application. This method can be applied to the network architecture shown in Figure 1. The method may include at least one of the following steps (610-620):

[0158] Step 610: The terminal device sends the first message.

[0159] Step 620: The terminal device calculates the first RNTI based on the time-frequency resources used by the first message.

[0160] Accordingly, the network device receives the first message sent by the terminal device; the network device calculates the first RNTI based on the time-frequency resources used by the first message.

[0161] Among them, the terminal equipment refers to the terminal equipment in the NTN TDD system, and the network equipment refers to the network equipment in the NTN TDD system.

[0162] In some embodiments, the first message is a message sent by the terminal device to the network device to establish a communication connection. Time-frequency resources include time-domain resources and frequency-domain resources. Time-domain resources refer to transmission resources that are divided and managed over time, and can be time slots, symbols, frames, subframes, etc. Frequency-domain resources refer to a frequency range used for data transmission, and can be carriers, subcarriers, RBs (Resource Blocks), etc.

[0163] In an NTN TDD system, time-frequency resources can be time-domain resources, and the basic unit of time-domain resources can be a time-domain unit, which can be a subframe or a time slot. The time-frequency resources used by the first message can be uplink time-domain resources, and the basic unit of uplink time-domain resources can be an uplink time-domain unit. An uplink time-domain unit can include an uplink time slot or an uplink subframe. The uplink time slot refers to the time slot divided in the NTN TDD system, and the uplink time slot includes at least one uplink subframe. In an NTN TDD system, a TDD frame can include multiple uplink time-domain units, and the first message is transmitted in an available uplink time-domain unit among the multiple uplink time-domain units. In other words, the first message cannot be transmitted in an unavailable uplink time-domain unit among the multiple uplink time-domain units. For example, as shown in Figure 5, a TDD frame includes multiple uplink time slots (UL1, UL2, UL3, UL4), where one uplink time slot can correspond to 8.28ms, and one uplink time slot can include 8 uplink subframes. The available uplink time domain unit can be any one of the uplink time slots UL1, UL2, UL3, and UL4. For example, if the available uplink time domain unit is UL1, it means that the first message can only be sent in at least one uplink subframe in UL1. That is, the uplink transmission for the first message can only use 8 consecutive uplink subframes within every 90ms (i.e., each TDD frame) (e.g., the 8 consecutive uplink subframes included in UL1).

[0164] In some embodiments, the period of the transmission resource corresponding to the first message is an integer multiple of the first duration. In some embodiments, the first duration is 90ms or 9 radio frames.

[0165] The transmission period of the first message refers to the repetition time interval of the transmission resources used to send the first message. A radio frame is the basic unit of time, used to organize and manage data transmission in wireless communication. A radio frame can be 10ms long and can be divided into multiple subframes, for example, 10 subframes, each 1ms long. For example, the period of the transmission resources corresponding to the first message can be 90ms, 180ms, 270ms, etc. If the transmission period is 90ms, it means the first message can be repeatedly sent every 90ms. The above method, by setting the period of the transmission resources corresponding to the first message to an integer multiple of the first duration, ensures that all uplink transmissions in the cell can only periodically use specific time-frequency resources (i.e., available uplink time domain units).

[0166] In some embodiments, the first message can be Msg1, and the time-frequency resource for sending Msg1 can be PRACH. The first RNTI is RA-RNTI. On one hand, the network device calculates the RA-RNTI based on the PRACH resource corresponding to Msg1, and uses the RA-RNTI to scramble the PDCCH to indicate the scheduled RAR PDSCH message. On the other hand, the terminal device calculates the RA-RNTI based on the PRACH resource for sending Msg1, and listens to the PDCCH scrambled by the RA-RNTI to ensure accurate reception of the RAR PDSCH message scheduled by the PDCCH.

[0167] In some embodiments, the first message can be Msg3, and the time-frequency resource for sending Msg3 can be PUSCH. On one hand, the network device calculates the first RNTI based on the PUSCH resource corresponding to Msg3, and uses the RA-RNT to scramble the PDCCH to indicate the scheduled Msg4PDSCH message. On the other hand, the terminal device calculates the first RNTI based on the PUSCH resource for sending Msg3, and listens to the PDCCH scrambled by the first RNTI to ensure accurate reception of the Msg4 PDSCH message scheduled by the PDCCH.

[0168] In summary, the technical solution provided in this application, for an NTN TDD system, can accurately calculate the first RNTI based on the time-frequency resources used by the first message. This facilitates the terminal device's subsequent monitoring of the PDCCH associated with the first RNTI, thereby determining the reception status of the first message.

[0169] The following describes how the first RNTI is determined.

[0170] In some embodiments, the first RNTI is determined based on at least one of the following: the identifier of the first SFN corresponding to the time-frequency resources used by the first message; the identifier of the first H-SFN corresponding to the time-frequency resources used by the first message; the minimum period supported by the transmission resources corresponding to the first message; the duration of the time window or timer used by the second message, wherein the second message is a response message corresponding to the first message; the identifier of the carrier used by the first message; and the identifier of the subcarrier used by the first message.

[0171] In some embodiments, the SFN identifier is used to indicate the number of a radio frame in a wireless communication system for synchronization and time management. The SFN identifier can be represented by 10 bits, meaning the SFN value can range from 0 to 1023. There can be a one-to-one correspondence between SFN and radio frames; that is, one SFN corresponds to one radio frame, and different SFNs correspond to different radio frames. For example, SFN = 0 can represent the 0th radio frame (e.g., 0 to 9 ms). SFN = 1 represents the 1st radio frame (e.g., 10 to 19 ms), but this application does not limit this. The SFN count range is 0 to 1023, with a total of 1024 radio frames constituting one SFN cycle. In other words, when the SFN reaches 1023, it returns to 0 and the counting restarts. In some embodiments, an H-SFN can include 1024 SFNs, meaning the duration of one H-SFN is the duration of 1024 radio frames.

[0172] In some embodiments, the time-frequency resources used by the first message may correspond to one SFN or multiple SFNs. When the time-frequency resources used by the first message correspond to one SFN, the first SFN is that SFN. When the time-frequency resources used by the first message correspond to multiple SFNs, the first SFN refers to the SFN corresponding to the start of transmission of the first message. In some embodiments, the time-frequency resources used by the first message may correspond to one H-SFN or multiple H-SFNs. When the time-frequency resources used by the first message correspond to one H-SFN, the first H-SFN is that H-SFN. When the time-frequency resources used by the first message correspond to multiple H-SFNs, the first H-SFN refers to the H-SFN corresponding to the start of transmission of the first message.

[0173] The minimum period supported by the transmission resources corresponding to the first message refers to the minimum repetition time interval of the transmission resources used to send the first message, for example, 90ms. In an NTN TDD system, the time-frequency resources used by the first message need to match the uplink subframes in the TDD frame structure to ensure that the first message is transmitted in the appropriate uplink subframe. In some embodiments, the duration of the time window used for the second message refers to a fixed time interval for receiving the second message. When the first message is Msg1 and the second message is RAR, the time window is the RAR time window. The timer is used to manage timeout processing and status updates for the response to the first message (i.e., the second message). When the first message is Msg3 and the second message is Msg4, the timer can be a contention resolution timer. Within the duration of the contention resolution timer, if the terminal device fails to successfully receive the second message, i.e., the conflict resolution fails, the contention resolution timer can trigger timeout processing, such as retransmitting Msg.

[0174] The carrier identifier used for the first message is a unique identifier for the radio carrier used to transmit the first message, used to distinguish different frequency resources. In some embodiments, a carrier may include multiple subcarriers, which together constitute the frequency resources of that carrier. The subcarrier identifier used for the first message is a unique identifier within that carrier specifically used to transmit the first message; it is used to identify the specific transmission resource for transmitting the first message at a finer granular level.

[0175] The above method can flexibly determine the first RNTI based on the time-frequency characteristics, periodicity, carrier and subcarrier identification, and the duration settings of the corresponding timer or time window of the transmission resource.

[0176] The following describes in detail how the first RNTI is determined in two scenarios. Scenario 1: The first message is Msg1; Scenario 2: The first message is Msg3.

[0177] Scenario 1, the first message is Msg1

[0178] In some embodiments, Msg1 may refer to a message during the random access process.

[0179] In some embodiments, the first message is Msg1, and the first RNTI is a RA-RNTI. In some embodiments, the first message is Msg1, and the first RNTI is determined based on at least one of the following: the identifier of the first SFN corresponding to the PRACH resource used by Msg1; the identifier of the first H-SFN corresponding to the PRACH resource used by Msg1; the minimum period supported by the PRACH resource; the duration of the RAR window; and the identifier of the carrier used by Msg1.

[0180] The minimum period supported by PRACH resources indicates the minimum time interval for PRACH resource repetition. In NTN TDD systems, PRACH resources are typically configured within specific subframes, which are called PRACH subframes. The selection and configuration of PRACH subframes need to match the uplink subframes in the TDD frame structure to ensure that PRACH resources are available within the appropriate time period. The method described above, through this minimum period, ensures that the allocation of RA-RNTI matches the PRACH resource configuration in the TDD mode frame structure.

[0181] The RAR window refers to the time window for receiving random access response messages. The duration of this RAR window defines the time limit within which the terminal device can receive RAR messages. By considering the duration of the RAR window, it can be ensured that the allocation of RA-RNTI is synchronized with the RAR message reception time window, thereby improving response efficiency and reliability. By considering the carrier identifier used by Msg1, it can be ensured that the allocation of RA-RNTI is associated with a specific carrier, enabling finer-grained spectrum resource management and scheduling.

[0182] The above method, for the random access procedure of NTN TDD system, fully considers the time-frequency characteristics, periodicity, RAR window duration, and carrier identification of the PRACH resource used by Msg1, and can flexibly and accurately determine the first RNTI (RA-RNTI) to ensure the reliability of the random access procedure.

[0183] In some embodiments, when the maximum duration of the RAR window is less than or equal to the length of an H-SFN, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * carrier_id_1; or, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1); where SFN_id_1 is the identifier of the first SFN corresponding to the PRACH resource used to transmit Msg1; Tmin_1 is the minimum period supported by the PRACH resource; M is a predefined value; and carrier_id_1 is the identifier of the carrier used to transmit Msg1.

[0184] In some embodiments, when the maximum duration of the RAR window is less than or equal to the length of an H-SFN and multi-carrier transmission of Msg1 is supported, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * carrier_id_1. In some embodiments, when the maximum duration of the RAR window is less than or equal to the length of an H-SFN and multi-carrier transmission of Msg1 is not supported, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1).

[0185] The above method, when supporting multi-carrier transmission of Msg1, requires adding a carrier identifier to the first RNTI calculation to distinguish Msg1 transmissions on different carriers. In a single-carrier system, all Msg1 transmissions occur on the same carrier, therefore no additional carrier identifier is needed, simplifying the calculation of the first RNTI.

[0186] In some embodiments, floor represents flooring down, where floor(SFN_id_1 / Tmin_1) means SFN_id_1 divided by Tmin_1 and then floored down. SFN_id_1 represents the identifier of the first SFN corresponding to the PRACH resource used to send Msg1. For NTN TDD systems, since the transmission of PRACH resources is not continuous and only occurs periodically at specific points in time, there are large time intervals between the values ​​of SFN_id_1, such as 90ms, 180ms, 270ms, etc. If SFN_id_1 is used directly to calculate the first RNTI, the value of the first RNTI will be too scattered, that is, the value distribution range of the first RNTI is too wide, thus wasting resources.

[0187] The above method, by dividing SFN_id_1 by Tmin_1 (the minimum period supported by PRACH resources), can map SFN_id_1 to a smaller numerical range, thereby making the calculated value of the first RNTI more concentrated.

[0188] In some embodiments, when the maximum duration of the RAR window is greater than the length of an H-SFN, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * carrier_id_1 + K1 * (H-SFN_id_1 mod L1); or, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * (H-SFN_id_1 mod L1); where SFN_id_1 is the identifier of the first SFN corresponding to the PRACH resource used to transmit Msg1; H-SFN_id_1 is the identifier of the first H-SFN corresponding to the PRACH resource used to transmit Msg1; Tmin_1 is the minimum period supported by the PRACH resource; M, K1, and L1 are all predefined values; and carrier_id_1 is the identifier of the carrier used to transmit Msg1.

[0189] The modulo operation is used to find the remainder when two numbers are divided. Since the maximum duration of the RAR window is greater than the length of an H-SFN, H-SFN_id_1 will span multiple H-SFNs. By using H-SFN_id_1 mod L1, the H-SFN_id_1 spanning multiple periods can be mapped to the range 0 to L1-1. This ensures the accuracy of the first RNTI calculation while mapping H-SFN_id to a smaller range, ensuring a concentrated distribution of the first RNTI values.

[0190] In some embodiments, L1 is the maximum duration of the RAR window. That is, H-SFN_id_1 mod L1 represents the maximum duration of the RAR window as H-SFN_id_1 mod L1, ensuring that H-SFN_id_1 is mapped to a single RAR window.

[0191] In some embodiments, when the maximum duration of the RAR window is greater than the length of an H-SFN and multi-carrier transmission of Msg1 is supported, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * carrier_id_1 + K1 * (H-SFN_id_1 mod L1). In some embodiments, when the maximum duration of the RAR window is greater than the length of an H-SFN and multi-carrier transmission of Msg1 is not supported, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * (H-SFN_id_1 mod L1).

[0192] In some embodiments, K1 is related to the maximum number of carriers Ncarrier supported for transmitting Msg1. The maximum number of carriers supported for Msg1 refers to the maximum number of carriers that the terminal device can use during the transmission of Msg1. That is, the terminal device can transmit Msg1 on these Ncarrier carriers. Optionally, K1 = M * Ncarrier.

[0193] The above method, by setting K1 to be related to the maximum number of carriers supported by the transmission Msg1, can avoid first RNTI value conflicts between different carriers in a multi-carrier system.

[0194] In some embodiments, when the maximum duration of the RAR window is less than or equal to the length of an H-SFN, M = ceiling(RAR window duration / Tmin_1). When the maximum duration of the RAR window is greater than the length of an H-SFN, M = ceiling(length of an H-SFN / Tmin_1). Here, ceiling represents rounding up.

[0195] The above method determines M by using the smaller value between the duration of the RAR window and the length of an H-SFN, further ensuring that the calculated values ​​of the first RNTI are uniformly concentrated.

[0196] In some embodiments, the method further includes: after sending Msg1, starting a RAR window; and during the operation of the RAR window, listening to the PDCCH scrambled by the first RNTI within the available downlink time domain unit.

[0197] In the NTN TDD system, a time-domain unit is either a subframe or a time slot. Available downlink time-domain units refer to the time-domain resources that a terminal device can use to listen to the PDCCH scrambled by the first RNTI in the NTN TDD system. In other words, a TDD frame structure includes multiple downlink time-domain units, but only some of these units are available. The terminal device can only listen to the PDCCH scrambled by the first RNTI within these available downlink time-domain units. As shown in Figure 5, in the NTN TDD system, a TDD frame structure can include multiple downlink time slots (DL1, DL2, DL3, DL4). These downlink time slots refer to the time slots allocated in the NTN TDD system. One downlink time slot can correspond to 8.28 ms, and one downlink time slot can include at least one downlink subframe. The terminal device can listen to the PACCH scrambled by the first RACH in any subframe of any of the downlink time slots (DL1, DL2, DL3, DL4). For example, if a terminal device can listen to the PACCH scrambled by the first RACH in a subframe of DL1, then DL1 is a usable downlink time unit. In other words, downlink transmission for the PACCH scrambled by the first RACH can only use 8 consecutive downlink subframes within every 90ms.

[0198] The above method ensures the reliability of PDCCH reception by listening to the PDCCH scrambled by the first RNTI in the available downlink time domain unit.

[0199] In some embodiments, if the first time point is within an available downlink time domain unit, the start time of the RAR window is the first time point; if the first time point is outside an available downlink time domain unit, the start time of the RAR window is the first available downlink time domain unit after the first time point.

[0200] If the first moment falls within an available downlink time domain unit (LDU), the RAR window will immediately start at that moment to ensure timely monitoring of the PDCCH scrambled by the first RNTI, thereby ensuring the reliability of the PDCCH reception. If the first moment does not fall within an available downlink time domain unit, the RAR window will start at the first available downlink time domain unit after the first moment. The first available downlink time domain unit after the first moment refers to checking each downlink time domain unit sequentially according to the timing arrangement of the TDD frame structure, starting from the first moment, until a downlink time domain unit in an available state is found. This downlink time domain unit is the first available downlink time domain unit after the first moment. For example, as shown in Figure 5, the available downlink time domain unit can be DL4, and the first moment can fall within DL1. In this case, the RAR window will start at the first available downlink time domain unit DL4 after DL1.

[0201] The above method enables the RAR window startup time to be well matched with the frame structure of TDD mode. Specifically, it can flexibly adjust the RAR window startup timing based on whether the first moment falls within an available downlink time domain unit. If the first moment happens to fall within an available downlink time domain unit, it is directly used as the RAR window startup time to receive the PDCCH in a timely manner, thereby reducing latency. If the first moment is outside an available downlink time domain unit, the RAR window startup time is the first available downlink time domain unit after the first moment. This method helps reduce the power consumption of the terminal device because the terminal device does not need to perform unnecessary listening on unavailable downlink time domain units, but only needs to listen on available downlink time domain units, thereby reducing power consumption.

[0202] In some embodiments, the first moment is determined based on the moment when the terminal device sends Msg1. In some embodiments, the first moment is the last subframe in which the terminal device sends Msg1 plus X subframes, plus the round-trip delay between the terminal device and the network device; where X is a predefined value.

[0203] The round-trip time between a terminal device and a network device refers to the delay time from when the terminal device sends the first message to when it receives a response from the network device. The last subframe in which the terminal device sends Msg1 refers to the last subframe in which the terminal device completes the transmission of Msg1. In other words, it refers to the last portion of transmission resources used by the terminal device when sending Msg1, usually divided in units of subframes. For example, as shown in Figure 5, the available uplink time domain unit can be UL1, which can include eight consecutive uplink subframes, namely subframes 0 to 7. The terminal device can use subframes 0 to 3 in UL1 to transmit the first message, so the last subframe in which Msg1 is sent is subframe 3 in UL1. Table 1 below shows the value of X in NB-IoT (Narrowband Internet of Things) systems under different modes (TDD / FDD), different preamble formats, and different NPRACH retransmission numbers. Specifically, each row in Table 1 describes the specific value of X under specific conditions.

[0204] Table 1

[0205] The above method enhances the accuracy of the first moment determination by comprehensively considering the last subframe of Msg1 sent by the terminal device, the predefined X value, and the round-trip delay between the terminal device and the network device.

[0206] In some embodiments, the RAR window starts at the first available downlink time domain unit after the first time unit. In some embodiments, regardless of whether the first time unit is within an available downlink time domain unit, the RAR window starts at the first available downlink time domain unit after the first time unit. The above method is relatively simple, as it does not require determining whether the first time unit is within an available downlink time domain unit, and directly adjusts to the next available time domain unit. In some embodiments, the RAR window starts at the first available downlink time domain unit no earlier than the first time unit. The above method, by ensuring that the RAR window starts no earlier than the first available downlink time domain unit of the first time unit, can guarantee that the terminal device will not start the RAR window prematurely, thereby reducing terminal power consumption.

[0207] Scenario 2, the first message is Msg3

[0208] In some embodiments, Msg3 may refer to a message in the CB-Msg3 based EDT process or a message in the random access process; this application does not limit this.

[0209] In some embodiments, the first message is Msg3, and the first RNTI is determined based on at least one of the following: the identifier of the first SFN corresponding to the PUSCH resource used by Msg3; the identifier of the first H-SFN corresponding to the PUSCH resource used by Msg3; the minimum period supported by the PUSCH resource; the duration of the contention resolution timer; the identifier of the carrier used by Msg3; and the identifier of the subcarrier used by Msg3.

[0210] The contention resolution timer, which can be mac-ContentionResolutionTimer, is used to define a time period for waiting for contention resolution. During a random access procedure or EDT, after the terminal device sends Msg3, it starts the contention resolution timer, waiting for a response from the network device, i.e., Msg4 (contention resolution message). If Msg4 is received before the contention resolution timer expires, the contention resolution is successful; otherwise, the random access procedure may need to be re-initiated, for example, by retransmitting Msg3.

[0211] The above method, through SFN and H-SFN identifiers based on PUSCH resources and minimum period, ensures that the allocation of RNTI matches the frame structure and time synchronization of the NTN TDD system. In multi-carrier systems, using different carrier and subcarrier identifiers helps distinguish transmission resources on different frequency bands, avoiding interference and collisions. The duration of the contention resolution timer is a crucial parameter for ensuring the reliability of the random access process. It ensures that the terminal device has sufficient time to wait for the network device's response, while avoiding indefinite waiting. By correlating the determination of the first RNTI with the above parameters, more efficient and reliable random access management can be achieved.

[0212] In some embodiments, when the maximum duration of the contention resolution timer is less than or equal to the length of one H-SFN, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + M*carrier_id_2; or, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id; where SFN_id_2 is the identifier of the first SFN corresponding to the PUSCH resource used to transmit Msg3; Tmin_2 is the minimum period supported by the PUSCH resource; N and M are predefined values; subcarrier_id is the identifier of the subcarrier used to transmit Msg3; and carrier_id_2 is the identifier of the carrier used to transmit Msg3.

[0213] In some embodiments, floor(SFN_id_2 / Tmin_2) represents SFN_id_2 divided by Tmin_2 and then rounded down. SFN_id_2 represents the identifier of the first SFN corresponding to the PUSCH resource used to send Msg3. For NTN TDD systems, since the transmission of PUSCH resources is not continuous and only occurs periodically at specific points in time, there are large time intervals between the values ​​of SFN_id_2, such as 90ms, 180ms, 270ms, etc. If SFN_id_2 is used directly to calculate the first RNTI, the value of the first RNTI will be too scattered, that is, the range of the first RNTI value is too wide, thus wasting resources.

[0214] The above method, by dividing SFN_id_2 by Tmin_2 (the minimum period supported by PUSCH resources), can map SFN_id_2 to a smaller numerical range, thereby making the calculated value of the first RNTI more concentrated.

[0215] In some embodiments, when the maximum duration of the contention resolution timer is less than or equal to the length of an H-SFN and multi-carrier transmission of Msg3 is supported, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + M*carrier_id_2. In some embodiments, when the maximum duration of the contention resolution timer is less than or equal to the length of an H-SFN and multi-carrier transmission of Msg3 is not supported, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id.

[0216] The above method, when supporting multi-carrier transmission of Msg3, requires adding a carrier identifier to the first RNTI calculation to distinguish Msg3 transmissions on different carriers. In a single-carrier system, all Msg3 transmissions occur on the same carrier, therefore no additional carrier identifier is needed, simplifying the calculation of the first RNTI.

[0217] In some embodiments, when the maximum value of the contention resolution timer is greater than the length of an H-SFN, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + P*carrier_id_2 + K2*(H-SFN_id_2 mod L2); or, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + P*(H-SFN_id_2 mod L2); where SFN_id_2 is the identifier of the first SFN corresponding to the PUSCH resource used to transmit Msg3; H-SFN_id_2 is the identifier of the first H-SFN corresponding to the PUSCH resource used to transmit Msg3; Tmin_2 is the minimum period supported by the PUSCH resource; N, P, K2 and L2 are all predefined values; subcarrier_id is the identifier of the subcarrier used to transmit Msg3; and carrier_id_2 is the identifier of the carrier used to transmit Msg3.

[0218] In some embodiments, since the maximum duration of the contention resolution timer is greater than the length of an H-SFN, H-SFN_id_2 may span multiple H-SFNs. By using H-SFN_id_2 mod L2, the H-SFN_id_2 spanning multiple cycles can be mapped to the range of 0 to L2-1. This ensures the accuracy of the calculation of the first RNTI while mapping H-SFN_id_2 to a smaller range, ensuring that the value of the first RNTI is concentrated.

[0219] In some embodiments, L2 is the maximum value of the contention resolution timer duration. That is, H-SFN_id_2 mod L2 is the maximum value of H-SFN_id_2 mod the contention resolution timer duration, ensuring that H-SFN_id_2 is mapped to a contention resolution timer duration range.

[0220] In some embodiments, K2 is related to the maximum number of carriers Ncarrier_2 supported for transmitting Msg3. The maximum number of carriers supported for Msg3 refers to the maximum number of carriers that the terminal device can use during the transmission of Msg3. That is, the terminal device can transmit Msg3 on these Ncarrier_2 carriers. Optionally, K2 = P * Ncarrier_2.

[0221] The above method, by setting K2 to be related to the maximum number of carriers supported by the transmission Msg3, can avoid first RNTI value conflicts between different carriers in a multi-carrier system.

[0222] In some embodiments, a contention resolution timer is started or restarted after each transmission of Msg3. Specifically, if the second time point falls within an available downlink time domain unit, the time at which the contention resolution timer is started or restarted is the second time point; if the second time point falls outside an available downlink time domain unit, the time at which the contention resolution timer is started or restarted is the first available downlink time domain unit after the second time point. The second time point is determined based on the time when the terminal device transmits Msg3.

[0223] If the second time step happens to fall within an available downlink time domain unit, the contention resolution timer will immediately start or restart at the second time step to ensure timely monitoring of the PDCCH scrambled by the first RNTI, thereby ensuring the reliability of the PDCCH reception. If the second time step does not fall within an available downlink time domain unit, the contention resolution timer will start at the first available downlink time domain unit after the second time step. The first available downlink time domain unit after the second time step refers to the downlink time domain unit that is checked sequentially according to the timing sequence of the TDD frame structure, starting from the second time step, until a downlink time domain unit in a usable state is found. This downlink time domain unit is the first available downlink time domain unit after the second time step.

[0224] The above method allows the start or restart time of the contention resolution timer to be well matched with the frame structure of TDD mode. Specifically, it can flexibly adjust the start timing of the contention resolution timer based on whether the second time interval falls within an available downlink time domain unit. If the second time interval happens to fall within an available downlink time domain unit, it is directly used as the start time of the contention resolution timer to receive the PDCCH in a timely manner, thereby reducing latency. If the second time interval is outside an available downlink time domain unit, the start time of the contention resolution timer is the first available downlink time domain unit after the second time interval. This method helps reduce the power consumption of the terminal device because the terminal device does not need to perform unnecessary listening on unavailable downlink time domain units, but only needs to listen on available downlink time domain units, thereby reducing power consumption.

[0225] In some embodiments, the second time point is the time when the terminal device sends the last subframe of Msg3 plus the round-trip delay between the terminal device and the network device. The last subframe of Msg3 sent by the terminal device refers to the last subframe in which the terminal device completes the transmission of Msg3. The above method enhances the accuracy of the second time point determination by comprehensively considering both the last subframe of Msg3 sent by the terminal device and the round-trip delay between the terminal device and the network device.

[0226] In some embodiments, the contention resolution timer is started or restarted at the first available downlink time domain unit after the second time unit. In some embodiments, regardless of whether the second time unit is within an available downlink time domain unit, the contention resolution timer is started at the first available downlink time domain unit after the second time unit. The above method is relatively simple, as it does not require determining whether the second time unit is within an available downlink time domain unit, and directly adjusts to the next available time domain unit.

[0227] In some embodiments, the time to start or restart the contention resolution timer is no earlier than the first available downlink time domain unit of the second time period. By ensuring that the start time of the contention resolution timer is no earlier than the first available downlink time domain unit of the second time period, the above method can guarantee that the terminal device will not start the contention resolution timer prematurely, thereby reducing terminal power consumption.

[0228] Please refer to Figure 7, which shows a flowchart of a wireless communication method provided in another embodiment of this application. This method can be applied to the network architecture shown in Figure 1. The method may include at least one of the following steps (710-720):

[0229] Step 710: The network device does not send PDCCH on the available downlink time domain units within the time interval of the first channel or signal transmission.

[0230] Step 720: The terminal device does not listen to the PDCCH on the available downlink time domain units located within the time interval of the first channel or signal transmission.

[0231] Among them, the terminal equipment refers to the terminal equipment in the NTN TDD system, and the network equipment refers to the network equipment in the NTN TDD system.

[0232] In some embodiments, the time-domain unit is a subframe or a time slot. As shown in FIG5, the time-domain unit includes an uplink time-domain unit and a downlink time-domain unit. The uplink time-domain unit can be an uplink time slot, such as UL1, UL2, UL3, and UL4. This uplink time slot is a time slot defined in the NTN TDD system, and each uplink time slot can include at least one uplink subframe. For example, UL1 can include 8 uplink subframes. The uplink time-domain unit can also be an uplink subframe. The downlink time-domain unit can be a downlink time slot, such as DL1, DL2, DL3, and DL4. This downlink time slot is a time slot defined in the NTN TDD system, and each downlink time slot can include at least one downlink subframe. For example, DL1 can include 8 downlink subframes. The downlink time-domain unit can also be a downlink subframe.

[0233] In some embodiments, the first channel or signal is a first uplink channel or signal, and the transmission of the first uplink channel or signal is distributed across multiple uplink time domain units; not transmitting PDCCH on available downlink time domain units within the time interval of the transmission of the first channel or signal includes: not transmitting PDCCH on available downlink time domain units located between multiple uplink time domain units.

[0234] Available downlink time domain units (PDCCHs) between multiple uplink time domain units refer to the available downlink time domain units between the first and last uplink time domain units. During the time interval between multiple uplink time domain units, network devices may be receiving and processing uplink data transmissions, or performing uplink / downlink resource switching and management operations. Since these operations take time, the network devices are not ready to send downlink control information to the terminal devices during this time interval; therefore, these available downlink time domain units do not contain valid PDCCH information.

[0235] In some embodiments, the first channel or signal is a first uplink channel or signal, and the transmission of the first uplink channel or signal is distributed across multiple uplink time domain units; not listening to the PDCCH on available downlink time domain units within the time interval of the transmission of the first channel or signal includes: not listening to the PDCCH on available downlink time domain units located between multiple uplink time domain units.

[0236] For example, as shown in FIG8, a schematic diagram of two TDD frames provided in an embodiment of this application is illustrated. TDD frame 1 and TDD frame 2 are two consecutive TDD frames, and DL1 in each TDD frame can be an available downlink time domain unit. The first uplink channel or signal transmission is distributed in the two uplink time domain units, such as UL1 in TDD frame 1 and UL1 in TDD frame 2. Therefore, PDCCH is not monitored on DL1 in TDD frame 1 between UL1 in TDD frame 1 and UL1 in TDD frame 2.

[0237] The above method can save power consumption of terminal devices by not listening to the PDCCH on the available downlink time domain units located between multiple uplink time domain units.

[0238] In some embodiments, the first uplink channel or signal is PUSCH or PRACH. In some embodiments, the first uplink channel or signal being PUSCH corresponds to the case where the first message is Msg3. In some embodiments, PUSCH can also be used to transmit other types of messages, which is not limited in this application. The first uplink channel or signal being PRACH corresponds to the case where the first message is Msg1. In some embodiments, PUSCH or PRACH transmission can be distributed across multiple uplink time domain units. On available downlink time domain units located between multiple uplink time domain units, PDCCH is not monitored.

[0239] In some embodiments, the first channel or signal is a first downlink channel or signal, and the transmission of the first downlink channel or signal is distributed across multiple downlink time domain units; not transmitting PDCCH on available downlink time domain units within the time interval of the transmission of the first channel or signal includes: not transmitting PDCCH on available downlink time domain units located between multiple downlink time domain units.

[0240] Available downlink time domain units located between multiple downlink time domain units refer to the available downlink time domain units between the first downlink time domain unit transmitting the first downlink channel or signal and the last downlink time domain unit.

[0241] On available downlink time domain units (MTBs) between multiple downlink time domain units, the network device is processing the transmission of the first downlink channel or signal, or preparing for the transmission of the next downlink channel or signal. On the one hand, the network device may not be ready to send valid PDCCH information to the terminal device at this time, so sending PDCCH is unnecessary and would only waste downlink time domain resources. On the other hand, sending PDCCH at this time may conflict with these operations, leading to signal interference or data loss. Therefore, the network device does not send PDCCH on available downlink time domain units located between multiple downlink time domain units.

[0242] In some embodiments, the first downlink channel or signal is PDSCH. PDSCH transmission is distributed across multiple downlink time domain units; PDCCH is not monitored on available downlink time domain units within the time interval of PDSCH transmission, including: not monitoring PDCCH on available downlink time domain units located between multiple downlink time domain units.

[0243] In some embodiments, the first channel or signal is a first downlink channel or signal, and the transmission of the first downlink channel or signal is distributed across multiple downlink time domain units; not listening to the PDCCH on available downlink time domain units within the time interval of the transmission of the first channel or signal includes: not listening to the PDCCH on available downlink time domain units located between multiple downlink time domain units.

[0244] For example, as shown in Figure 8, DL1 in each TDD frame can be an available downlink time domain unit. The first downlink channel or signal transmission is distributed in two downlink time domain units, such as DL1 in TDD frame 1 and DL1 in TDD frame 2. The available downlink time domain units among multiple downlink time domain units are DL1 in TDD frame 1 and DL1 in TDD frame 2. Then, PDCCH is not monitored on UL1 of TDD frame 1 and UL1 of TDD frame 2.

[0245] The above method can save power consumption of terminal devices by not listening to the PDCCH on available downlink time domain units located between multiple downlink time domain units.

[0246] In some embodiments, the method further includes: if the start time of the DRX persistence timer is within a first time period, the DRX persistence timer is not started; wherein the first time period is any continuous time period occupied by the first channel or signal transmission.

[0247] The first time period is the time interval between the start and end times of transmitting the first channel or signal. For example, the start time of the first time period can be the time corresponding to the first uplink / downlink subframe of transmitting the first channel or signal, and the end time of the first time period can be the time corresponding to the last uplink / downlink subframe of transmitting the first channel or signal.

[0248] In some embodiments, if the start time of the DRX persistence timer is during a PUSCH transmission (i.e., between the start and end times of the PUSCH transmission), the UE does not start the DRX persistence timer.

[0249] In some embodiments, if the start time of the DRX persistence timer is during a PDSCH transmission (i.e., between the start and end times of the PDSCH transmission), the UE does not start the DRX persistence timer.

[0250] In some embodiments, if the start time of the DRX persistence timer is during a PRACH transmission (i.e., between the start and end times of the PRACH transmission), the UE does not start the DRX persistence timer.

[0251] The above method can effectively avoid invalid PDCCH listening by the UE and save UE power consumption by not starting the DRX persistent timer during the first channel or signal transmission period (such as during PUSCH, PDSCH and PRACH transmission).

[0252] In summary, the technical solution provided by the embodiments of this application fully considers that if the network device does not send PDCCH on the available downlink time domain unit within the time interval of the first channel or signal transmission, the terminal device will not listen to PDCCH on the available downlink time domain unit, which can effectively avoid invalid PDCCH listening by the terminal device and save power consumption of the terminal device.

[0253] The above embodiments only describe the technical solution provided in this application from the perspective of interaction between terminal devices and network devices. The steps described above, performed by the terminal device, can be implemented independently as a wireless communication method on the terminal device side. Similarly, the steps described above, performed by the network device, can be implemented independently as a wireless communication method on the network device side.

[0254] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0255] Please refer to Figure 9, which shows a block diagram of a wireless communication device according to an embodiment of this application. This device has the function of implementing the above-described wireless communication method; the function can be implemented in hardware or by hardware executing corresponding software. This device can be the terminal device described above, or it can be located within a terminal device. As shown in Figure 9, the device 900 may include a transmitting module 910 and a processing module 920.

[0256] The sending module 910 is used to send the first message.

[0257] The processing module 920 is used to calculate the first RNTI based on the time-frequency resources used by the first message.

[0258] In some embodiments, the first RNTI is determined based on at least one of the following: the identifier of the first SFN corresponding to the time-frequency resources used by the first message; the identifier of the first H-SFN corresponding to the time-frequency resources used by the first message; the minimum period supported by the transmission resources corresponding to the first message; the duration of the time window or timer used by the second message, wherein the second message is a response message corresponding to the first message; the identifier of the carrier used by the first message; and the identifier of the subcarrier used by the first message.

[0259] In some embodiments, the first message is Msg1, and the first RNTI is determined based on at least one of the following: the identifier of the first SFN corresponding to the PRACH resource used by Msg1; the identifier of the first H-SFN corresponding to the PRACH resource used by Msg1; the minimum period supported by the PRACH resource; the duration of the Random Access Response (RAR) window; and the identifier of the carrier used by Msg1.

[0260] In some embodiments, when the maximum duration of the RAR window is less than or equal to the length of an H-SFN, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * carrier_id_1; or, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1); where SFN_id_1 is the identifier of the first SFN corresponding to the PRACH resource used to transmit Msg1; Tmin_1 is the minimum period supported by the PRACH resource; M is a predefined value; and carrier_id_1 is the identifier of the carrier used to transmit Msg1.

[0261] In some embodiments, when the maximum duration of the RAR window is greater than the length of an H-SFN, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * carrier_id_1 + K1 * (H-SFN_id_1 mod L1); or, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * (H-SFN_id_1 mod L1); where SFN_id_1 is the identifier of the first SFN corresponding to the PRACH resource used to transmit Msg1; H-SFN_id_1 is the identifier of the first H-SFN corresponding to the PRACH resource used to transmit Msg1; Tmin_1 is the minimum period supported by the PRACH resource; M, K1, and L1 are all predefined values; and carrier_id_1 is the identifier of the carrier used to transmit Msg1.

[0262] In some embodiments, K1 is related to the maximum number of carriers supported by transmitting Msg1.

[0263] In some embodiments, L1 is the maximum duration of the RAR window.

[0264] In some embodiments, when the maximum duration of the RAR window is less than or equal to the length of an H-SFN, M = ceiling(duration of the RAR window / Tmin_1); when the maximum duration of the RAR window is greater than the length of an H-SFN, M = ceiling(length of an H-SFN / Tmin_1).

[0265] In some embodiments, the device 900 further includes a receiving module (not shown in FIG9).

[0266] The receiving module is configured to start the RAR window after sending the Msg1; and during the operation of the RAR window, listen to the PDCCH scrambled by the first RNTI within the available downlink time domain unit.

[0267] In some embodiments, if the first time point is within an available downlink time domain unit, the start time of the RAR window is the first time point; if the first time point is outside an available downlink time domain unit, the start time of the RAR window is the first available downlink time domain unit after the first time point; or, the start time of the RAR window is the first available downlink time domain unit after the first time point; or, the start time of the RAR window is the first available downlink time domain unit no earlier than the first time point; wherein, the first time point is determined based on the time when the terminal device sends the Msg1.

[0268] In some embodiments, the first time is the time when the terminal device sends the last subframe of Msg1 plus X subframes, plus the round-trip delay between the terminal device and the network device; wherein, X is a predefined value.

[0269] In some embodiments, the first message is Msg3, and the first RNTI is determined based on at least one of the following: the identifier of the first SFN corresponding to the PUSCH resource used by Msg3; the identifier of the first H-SFN corresponding to the PUSCH resource used by Msg3; the minimum period supported by the PUSCH resource; the duration of the contention resolution timer; the identifier of the carrier used by Msg3; and the identifier of the subcarrier used by Msg3.

[0270] In some embodiments, when the maximum value of the contention resolution timer duration is less than or equal to the length of an H-SFN, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N * subcarrier_id + M * carrier_id_2; or, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N * subcarrier_id; where SFN_id_2 is the identifier of the first SFN corresponding to the PUSCH resource used to transmit Msg3; Tmin_2 is the minimum period supported by the PUSCH resource; N and M are predefined values; subcarrier_id is the identifier of the subcarrier used to transmit Msg3; and carrier_id_2 is the identifier of the carrier used to transmit Msg3.

[0271] In some embodiments, when the maximum value of the duration of the contention resolution timer is greater than the length of one H-SFN, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + P*carrier_id_2 + K2*(H-SFN_id_2 mod L2); or, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + P*(H-SFN_id_2 mod L2). L2); wherein, SFN_id_2 is the identifier of the first SFN corresponding to the PUSCH resource used to transmit Msg3; H-SFN_id_2 is the identifier of the first H-SFN corresponding to the PUSCH resource used to transmit Msg3; Tmin_2 is the minimum period supported by the PUSCH resource; N, P, K2 and L2 are all predefined values; subcarrier_id is the identifier of the subcarrier used to transmit Msg3; carrier_id_2 is the identifier of the carrier used to transmit Msg3.

[0272] In some embodiments, K2 is related to the maximum number of carriers supported by transmitting Msg3.

[0273] In some embodiments, L2 is the maximum duration of the contention resolution timer.

[0274] In some embodiments, the receiving module is configured to start or restart a contention resolution timer after each transmission of Msg3; wherein, if the second time is within an available downlink time domain unit, the time to start or restart the contention resolution timer is the second time; if the second time is outside an available downlink time domain unit, the time to start or restart the contention resolution timer is the first available downlink time domain unit after the second time; or, the time to start or restart the contention resolution timer is the first available downlink time domain unit after the second time; or, the time to start or restart the contention resolution timer is the first available downlink time domain unit no earlier than the second time; wherein the second time is determined based on the time when the terminal device transmits Msg3.

[0275] In some embodiments, the second time is the time when the terminal device sends the last subframe of Msg3 plus the round-trip delay between the terminal device and the network device.

[0276] In some embodiments, the time-domain unit is a subframe or a time slot.

[0277] In some embodiments, the period of the transmission resource corresponding to the first message is an integer multiple of the first duration.

[0278] In some embodiments, the first duration is 90ms or 9 wireless frames.

[0279] Please refer to Figure 10, which shows a block diagram of a wireless communication device according to another embodiment of this application. This device has the function of implementing the above-described wireless communication method; the function can be implemented in hardware or by hardware executing corresponding software. This device can be a network device as described above, or it can be located within a network device. As shown in Figure 10, the device 1000 may include a receiving module 1010 and a processing module 1020.

[0280] The receiving module 1010 is used to receive the first message.

[0281] The processing module 1020 calculates the first RNTI based on the time-frequency resources used by the first message.

[0282] In some embodiments, the first RNTI is determined based on at least one of the following: the identifier of the first SFN corresponding to the time-frequency resources used by the first message; the identifier of the first H-SFN corresponding to the time-frequency resources used by the first message; the minimum period supported by the transmission resources corresponding to the first message; the duration of the time window or timer used by the second message, wherein the second message is a response message corresponding to the first message; the identifier of the carrier used by the first message; and the identifier of the subcarrier used by the first message.

[0283] In some embodiments, the first message is Msg1, and the first RNTI is determined based on at least one of the following: the identifier of the first SFN corresponding to the PRACH resource used by Msg1; the identifier of the first H-SFN corresponding to the PRACH resource used by Msg1; the minimum period supported by the PRACH resource; the duration of the RAR window; and the identifier of the carrier used by Msg1.

[0284] In some embodiments, when the maximum duration of the RAR window is less than or equal to the length of an H-SFN, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * carrier_id_1; or, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1); where SFN_id_1 is the identifier of the first SFN corresponding to the PRACH resource used to transmit Msg1; Tmin_1 is the minimum period supported by the PRACH resource; M is a predefined value; and carrier_id_1 is the identifier of the carrier used to transmit Msg1.

[0285] In some embodiments, when the maximum duration of the RAR window is greater than the length of an H-SFN, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * carrier_id_1 + K1 * (H-SFN_id_1 mod L1); or, the first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * (H-SFN_id_1 mod L1); where SFN_id_1 is the identifier of the first SFN corresponding to the PRACH resource used to transmit Msg1; H-SFN_id_1 is the identifier of the first H-SFN corresponding to the PRACH resource used to transmit Msg1; Tmin_1 is the minimum period supported by the PRACH resource; M, K1, and L1 are all predefined values; and carrier_id_1 is the identifier of the carrier used to transmit Msg1.

[0286] In some embodiments, K1 is related to the maximum number of carriers supported by transmitting Msg1.

[0287] In some embodiments, L1 is the maximum duration of the RAR window.

[0288] In some embodiments, when the maximum duration of the RAR window is less than or equal to the length of an H-SFN, M = ceiling(duration of the RAR window / Tmin_1); when the maximum duration of the RAR window is greater than the length of an H-SFN, M = ceiling(length of an H-SFN / Tmin_1).

[0289] In some embodiments, the first message is Msg3, and the first RNTI is determined based on at least one of the following: the identifier of the first SFN corresponding to the PUSCH resource used by Msg3; the identifier of the first H-SFN corresponding to the PUSCH resource used by Msg3; the minimum period supported by the PUSCH resource; the duration of the contention resolution timer; the identifier of the carrier used by Msg3; and the identifier of the subcarrier used by Msg3.

[0290] In some embodiments, when the maximum value of the contention resolution timer duration is less than or equal to the length of an H-SFN, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N * subcarrier_id + M * carrier_id_2; or, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N * subcarrier_id; where SFN_id_2 is the identifier of the first SFN corresponding to the PUSCH resource used to transmit Msg3; Tmin_2 is the minimum period supported by the PUSCH resource; N and M are predefined values; subcarrier_id is the identifier of the subcarrier used to transmit Msg3; and carrier_id_2 is the identifier of the carrier used to transmit Msg3.

[0291] In some embodiments, when the maximum value of the duration of the contention resolution timer is greater than the length of one H-SFN, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + P*carrier_id_2 + K2*(H-SFN_id_2 mod L2); or, the first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + P*(H-SFN_id_2 mod L2). L2); wherein, SFN_id_2 is the identifier of the first SFN corresponding to the PUSCH resource used to transmit Msg3; H-SFN_id_2 is the identifier of the first H-SFN corresponding to the PUSCH resource used to transmit Msg3; Tmin_2 is the minimum period supported by the PUSCH resource; N, P, K2 and L2 are all predefined values; subcarrier_id is the identifier of the subcarrier used to transmit Msg3; carrier_id_2 is the identifier of the carrier used to transmit Msg3.

[0292] In some embodiments, K2 is related to the maximum number of carriers supported by transmitting Msg3.

[0293] In some embodiments, L2 is the maximum duration of the contention resolution timer.

[0294] In some embodiments, the device 1000 further includes a transmitting module (not shown in FIG10).

[0295] The sending module is used to send a second message based on the first RNTI, wherein the second message is a response message corresponding to the first message.

[0296] In some embodiments, the period of the transmission resource corresponding to the first message is an integer multiple of the first duration.

[0297] In some embodiments, the first duration is 90ms or 9 wireless frames.

[0298] Please refer to Figure 11, which shows a block diagram of a wireless communication device according to another embodiment of this application. This device has the function of implementing the above-described wireless communication method; the function can be implemented in hardware or by hardware executing corresponding software. This device can be the terminal device described above, or it can be disposed within a terminal device. As shown in Figure 11, the device 1100 may include a receiving module 1110.

[0299] The receiving module 1110 is configured not to listen to the PDCCH on the available downlink time domain units within the time interval of the first channel or signal transmission.

[0300] In some embodiments, the first channel or signal is a first uplink channel or signal, and the transmission of the first uplink channel or signal is distributed in a plurality of uplink time domain units; the receiving module 1110 is configured not to listen to the PDCCH on the available downlink time domain units located between the plurality of uplink time domain units.

[0301] In some embodiments, the first uplink channel or signal is PUSCH or PRACH.

[0302] In some embodiments, the first channel or signal is a first downlink channel or signal, and the transmission of the first downlink channel or signal is distributed in a plurality of downlink time domain units; the receiving module 1110 is configured not to listen to the PDCCH on the available downlink time domain units located between the plurality of downlink time domain units.

[0303] In some embodiments, the first downlink channel or signal is PDSCH.

[0304] In some embodiments, the receiving module 1110 is configured not to start the DRX continuous timer if the start time of the DRX continuous timer is within a first time period; wherein, the first time period is any continuous time period occupied by the first channel or signal transmission.

[0305] In some embodiments, the time-domain unit is a subframe or a time slot.

[0306] Please refer to Figure 12, which shows a block diagram of a wireless communication device according to another embodiment of this application. This device has the function of implementing the above-described wireless communication method; the function can be implemented in hardware or by hardware executing corresponding software. This device can be a network device as described above, or it can be located within a network device. As shown in Figure 12, the device 1200 may include a transmitting module 1210.

[0307] The transmitting module 1210 is configured not to transmit PDCCH on available downlink time domain units within the time interval of the first channel or signal transmission.

[0308] In some embodiments, the first channel or signal is a first uplink channel or signal, and the transmission of the first uplink channel or signal is distributed across multiple uplink time domain units; the transmitting module 1210 is configured not to transmit PDCCH on available downlink time domain units located between the multiple uplink time domain units.

[0309] In some embodiments, the first uplink channel or signal is PUSCH or PRACH.

[0310] In some embodiments, the first channel or signal is a first downlink channel or signal, and the transmission of the first downlink channel or signal is distributed across multiple downlink time domain units; the transmitting module 1210 is configured not to transmit PDCCH on available downlink time domain units located between the multiple downlink time domain units.

[0311] In some embodiments, the first downlink channel or signal is PDSCH.

[0312] In some embodiments, the time-domain unit is a subframe or a time slot.

[0313] It should be noted that the above embodiments only illustrate the division of the above functional modules when implementing the device. In actual applications, the above 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.

[0314] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here. For details not described in detail in the apparatus embodiments, please refer to the above method embodiments.

[0315] Please refer to Figure 13, which shows a schematic diagram of a communication device provided in one embodiment of this application. The communication device can be a terminal device or a network device as described above. The communication device 1300 may include a processor 1301, a transceiver 1302, and a memory 1303. The transceiver 1302 is used to implement sending or receiving functions, such as implementing the aforementioned sending and / or receiving functions, or implementing the functions of the aforementioned sending module and / or receiving module. The processor 1301 can be used to implement other processing functions or control sending and / or receiving, such as implementing the functions of the aforementioned processing module.

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

[0317] The transceiver 1302 may include a receiver and a transmitter. For example, the receiver and transmitter may be implemented as the same wireless communication component, which may include a wireless communication chip and a radio frequency antenna.

[0318] The memory 1303 can be connected to the processor 1301 and the transceiver 1302.

[0319] The memory 1303 can be used to store a computer program executed by the processor, and the processor 1301 is used to execute the computer program to implement the various steps in the above method embodiments.

[0320] In some embodiments, when the communication device 1300 is a terminal device, the transceiver 1302 is used to send a first message; the processor 1301 is used to calculate a first RNTI based on the time-frequency resources used by the first message.

[0321] In some embodiments, when the communication device 1300 is a network device, the transceiver 1302 is used to receive a first message; the processor 1301 is used to calculate a first RNTI based on the time-frequency resources used by the first message.

[0322] In some embodiments, when the communication device 1300 is a terminal device, the transceiver 1302 is configured not to listen to the PDCCH on the available downlink time domain units within the time interval of the first channel or signal transmission.

[0323] In some embodiments, when the communication device 1300 is a network device, the transceiver 1302 is configured not to transmit PDCCH on the available downlink time domain units within the time interval of the first channel or signal transmission.

[0324] For details not described in this embodiment, please refer to the embodiments above, which will not be repeated here.

[0325] Furthermore, the memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, including but not limited to: magnetic disks or optical disks, electrically erasable programmable read-only memory, erasable programmable read-only memory, statically accessible memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0326] This application also provides a computer-readable storage medium storing a computer program. The computer program is executed by a processor to implement the wireless communication method executed by the aforementioned terminal device or the wireless communication method executed by the aforementioned network device. In some embodiments, the computer-readable storage medium may include ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

[0327] This application also provides a chip, which includes programmable logic circuits and / or program instructions. When the chip is running, it is used to implement the wireless communication method executed by the aforementioned terminal device or the wireless communication method executed by the aforementioned network device.

[0328] This application also provides a chip, which includes programmable logic circuits and / or program instructions. When the chip is running in a terminal device, it is used to: send a first message; and calculate a first RNTI based on the time-frequency resources used by the first message. When the chip is running in the terminal device, it is also used to implement other steps executed by the terminal device as described in the above embodiments, which will not be repeated here.

[0329] This application also provides a chip, which includes programmable logic circuitry and / or program instructions. When the chip is running in a terminal device, it is used to: not listen to the PDCCH on available downlink time-domain units within a time interval of a first channel or signal transmission. When the chip is running in the terminal device, it is also used to implement other steps performed by the terminal device as described in the above embodiments, which will not be repeated here.

[0330] This application also provides a chip, which includes programmable logic circuitry and / or program instructions. When the chip is running in a network device, it is used to: receive a first message; and calculate a first RNTI based on the time-frequency resources used by the first message. When the chip is running in the network device, it is also used to implement other steps performed by the network device as described in the above embodiments, which will not be repeated here.

[0331] This application also provides a chip, which includes programmable logic circuitry and / or program instructions. When the chip is running in a network device, it is used to: not transmit PDCCH on available downlink time domain units within a time interval of a first channel or signal transmission. When the chip is running in the network device, it is also used to implement other steps performed by the network device as described in the above embodiments, which will not be repeated here.

[0332] This application also provides a computer program product, which includes computer instructions stored in a computer-readable storage medium. A processor reads and executes the computer instructions from the computer-readable storage medium to implement the wireless communication method executed by the terminal device or the wireless communication method executed by the network device.

[0333] It should be understood that the term "instruction" mentioned in the embodiments of this application can be a direct instruction, an indirect instruction, or an indication of a relationship. For example, A instructing B can mean that A directly instructs B, such as B being able to obtain information through A; it can also mean that A indirectly instructs B, such as A instructing C, so B can obtain information through C; or it can mean that there is a relationship between A and B.

[0334] In the description of the embodiments of this application, the term "correspondence" may indicate that there is a direct or indirect correspondence between two things, or that there is an association between two things, or that there is a relationship of instruction and being instructed, configuration and being configured, etc.

[0335] In some embodiments of this application, "predefined" can be achieved by pre-storing corresponding codes, tables, or other means that can be used to indicate relevant information in the device (e.g., including terminal devices and network devices). This application does not limit the specific implementation method. For example, predefined can refer to what is defined in the protocol.

[0336] In some embodiments of this application, the term "protocol" may refer to standard protocols in the field of communications, such as LTE protocols, NR protocols, and related protocols applied in future communication systems. This application does not limit the scope of these protocols.

[0337] In this article, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0338] In this article, "greater than or equal to" can mean greater than or equal to, and "less than or equal to" can mean less than or equal to.

[0339] Furthermore, the step numbers described herein are merely illustrative of one possible execution order between steps. In some other embodiments, the steps may not be executed in the order of their numbers, such as two steps with different numbers being executed simultaneously, or two steps with different numbers being executed in the reverse order of the illustration. This application does not limit this.

[0340] Those skilled in the art will recognize that the functions described in the embodiments of this application in one or more of the above examples 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 code on a computer-readable medium. Computer-readable media include computer storage media and communication media, wherein communication media include any medium that facilitates the transfer of a computer program from one place to another. Storage media can be any available medium that can be accessed by a general-purpose or special-purpose computer.

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

Claims

1. A wireless communication method, characterized in that, The method is performed by a terminal device in a non-terrestrial network (NTN) time-division duplex (TDD) system, and the method includes: Send the first message; Calculate the first wireless network temporary identifier (RNTI) based on the time-frequency resources used by the first message.

2. The method according to claim 1, characterized in that, The first RNTI is determined based on at least one of the following: The identifier of the first system frame number (SFN) corresponding to the time-frequency resource used by the first message; The identifier of the first supersystem frame number H-SFN corresponding to the time-frequency resources used by the first message; The minimum period supported by the transmission resources corresponding to the first message; The duration of the time window or timer used in the second message, where the second message is the response message corresponding to the first message; The identifier of the carrier used in the first message; The identifier of the subcarrier used in the first message.

3. The method according to claim 1 or 2, characterized in that, The first message is Msg1, and the first RNTI is determined based on at least one of the following: The identifier of the first SFN corresponding to the physical random access channel (PRACH) resource used by Msg1; The identifier of the first H-SFN corresponding to the PRACH resource used by Msg1; The minimum period supported by the PRACH resource; Duration of the random access response RAR window; The identifier of the carrier used by Msg1.

4. The method according to claim 3, characterized in that, When the maximum duration of the RAR window is less than or equal to the length of an H-SFN, The first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * carrier_id_1; or, The first RNTI = 1 + floor(SFN_id_1 / Tmin_1); Wherein, SFN_id_1 is the identifier of the first SFN corresponding to the PRACH resource used to transmit Msg1; Tmin_1 is the minimum period supported by the PRACH resource; M is a predefined value; and carrier_id_1 is the identifier of the carrier used to transmit Msg1.

5. The method according to claim 3 or 4, characterized in that, When the maximum duration of the RAR window is greater than the length of an H-SFN, The first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * carrier_id_1 + K1 * (H - SFN_id_1 mod L1); or, The first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M*(H - SFN_id_1 mod L1); Wherein, SFN_id_1 is the identifier of the first SFN corresponding to the PRACH resource used to transmit Msg1; H-SFN_id_1 is the identifier of the first H-SFN corresponding to the PRACH resource used to transmit Msg1; Tmin_1 is the minimum period supported by the PRACH resource; M, K1, and L1 are all predefined values; and carrier_id_1 is the identifier of the carrier used to transmit Msg1.

6. The method according to claim 5, characterized in that, K1 is related to the maximum number of carriers supported by transmitting Msg1.

7. The method according to claim 5 or 6, characterized in that, L1 is the maximum duration of the RAR window.

8. The method according to any one of claims 4 to 7, characterized in that, If the maximum duration of the RAR window is less than or equal to the length of an H-SFN, then M = ceiling(duration of the RAR window / Tmin_1); If the maximum duration of the RAR window is greater than the length of an H-SFN, then M = ceiling(length of an H-SFN / Tmin_1).

9. The method according to any one of claims 3 to 8, characterized in that, The method further includes: After sending Msg1, the RAR window is launched; During the operation of the RAR window, the physical downlink control channel (PDCCH) scrambled by the first RNTI is monitored within the available downlink time domain units.

10. The method according to claim 9, characterized in that, If the first time point is within an available downlink time domain unit, the start time of the RAR window is the first time point; if the first time point is outside an available downlink time domain unit, the start time of the RAR window is the first available downlink time domain unit after the first time point; or, The RAR window is started at the first available downlink time domain unit after the first time point; or, The RAR window is started no earlier than the first available downlink time domain unit at the first moment; The first moment is determined based on the moment when the terminal device sends Msg1.

11. The method according to claim 10, characterized in that, The first moment is the moment when the terminal device sends the last subframe of Msg1 plus X subframes, plus the round-trip delay between the terminal device and the network device; where X is a predefined value.

12. The method according to claim 1 or 2, characterized in that, The first message is Msg3, and the first RNTI is determined based on at least one of the following: The identifier of the first SFN corresponding to the Physical Uplink Shared Channel (PUSCH) resource used by Msg3; The identifier of the first H-SFN corresponding to the PUSCH resource used by Msg3; The minimum period supported by the PUSCH resource; The duration of the race condition timer; The identifier of the carrier used by Msg3; The identifier of the subcarrier used by Msg3.

13. The method according to claim 12, characterized in that, When the maximum duration of the contention resolution timer is less than or equal to the length of an H-SFN, The first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + M*carrier_id_2; or, The first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id; Wherein, SFN_id_2 is the identifier of the first SFN corresponding to the PUSCH resource used to transmit Msg3; Tmin_2 is the minimum period supported by the PUSCH resource; N and M are predefined values; subcarrier_id is the identifier of the subcarrier used to transmit Msg3; and carrier_id_2 is the identifier of the carrier used to transmit Msg3.

14. The method according to claim 12 or 13, characterized in that, When the maximum duration of the contention resolution timer is greater than the length of an H-SFN, The first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + P*carrier_id_2 + K2*(H-SFN_id_2mod L2); or, The first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + P*(H-SFN_id_2mod L2); Wherein, SFN_id_2 is the identifier of the first SFN corresponding to the PUSCH resource used to transmit Msg3; H-SFN_id_2 is the identifier of the first H-SFN corresponding to the PUSCH resource used to transmit Msg3; Tmin_2 is the minimum period supported by the PUSCH resource; N, P, K2, and L2 are all predefined values; subcarrier_id is the identifier of the subcarrier used to transmit Msg3; and carrier_id_2 is the identifier of the carrier used to transmit Msg3.

15. The method according to claim 14, characterized in that, K2 is related to the maximum number of carriers supported by transmitting Msg3.

16. The method according to claim 14 or 15, characterized in that, L2 is the maximum duration of the contention resolution timer.

17. The method according to any one of claims 3 to 16, characterized in that, The method further includes: After each Msg3 is sent, start or restart the contention resolution timer; Wherein, if the second time point is within an available downlink time domain unit, the time at which the contention resolution timer is started or restarted is the second time point; if the second time point is outside an available downlink time domain unit, the time at which the contention resolution timer is started or restarted is the first available downlink time domain unit after the second time point; or... The time to start or restart the contention resolution timer is the first available downlink time domain unit after the second time point; or, The time to start or restart the contention resolution timer is no earlier than the first available downlink time domain unit at the second time. The second time is determined based on the time when the terminal device sends Msg3.

18. The method according to claim 17, characterized in that, The second moment is the moment when the terminal device sends the last subframe of Msg3 plus the round-trip delay between the terminal device and the network device.

19. The method according to any one of claims 9, 10, and 17, characterized in that, The time-domain unit is a subframe or a time slot.

20. The method according to any one of claims 1 to 19, characterized in that, The period of the transmission resource corresponding to the first message is an integer multiple of the first duration.

21. The method according to claim 20, characterized in that, The first duration is 90ms or 9 wireless frames.

22. A wireless communication method, characterized in that, The method is performed by a network device in a non-terrestrial network (NTN) time-division duplex (TDD) system, and the method includes: Receive the first message; Calculate the first wireless network temporary identifier (RNTI) based on the time-frequency resources used by the first message.

23. The method according to claim 22, characterized in that, The first RNTI is determined based on at least one of the following: The identifier of the first system frame number (SFN) corresponding to the time-frequency resource used by the first message; The identifier of the first supersystem frame number H-SFN corresponding to the time-frequency resources used by the first message; The minimum period supported by the transmission resources corresponding to the first message; The duration of the time window or timer used in the second message, where the second message is the response message corresponding to the first message; The identifier of the carrier used in the first message; The identifier of the subcarrier used in the first message.

24. The method according to claim 22 or 23, characterized in that, The first message is Msg1, and the first RNTI is determined based on at least one of the following: The identifier of the first SFN corresponding to the physical random access channel (PRACH) resource used by Msg1; The identifier of the first H-SFN corresponding to the PRACH resource used by Msg1; The minimum period supported by the PRACH resource; Duration of the random access response RAR window; The identifier of the carrier used by Msg1.

25. The method according to claim 24, characterized in that, When the maximum duration of the RAR window is less than or equal to the length of an H-SFN, The first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * carrier_id_1; or, The first RNTI = 1 + floor(SFN_id_1 / Tmin_1); Wherein, SFN_id_1 is the identifier of the first SFN corresponding to the PRACH resource used to transmit Msg1; Tmin_1 is the minimum period supported by the PRACH resource; M is a predefined value; and carrier_id_1 is the identifier of the carrier used to transmit Msg1.

26. The method according to claim 24 or 25, characterized in that, When the maximum duration of the RAR window is greater than the length of an H-SFN, The first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M * carrier_id_1 + K1 * (H - SFN_id_1 mod L1); or, The first RNTI = 1 + floor(SFN_id_1 / Tmin_1) + M*(H - SFN_id_1 mod L1); Wherein, SFN_id_1 is the identifier of the first SFN corresponding to the PRACH resource used to transmit Msg1; H-SFN_id_1 is the identifier of the first H-SFN corresponding to the PRACH resource used to transmit Msg1; Tmin_1 is the minimum period supported by the PRACH resource; M, K1, and L1 are all predefined values; and carrier_id_1 is the identifier of the carrier used to transmit Msg1.

27. The method according to claim 26, characterized in that, K1 is related to the maximum number of carriers supported by transmitting Msg1.

28. The method according to claim 26 or 27, characterized in that, L1 is the maximum duration of the RAR window.

29. The method according to any one of claims 25 to 28, characterized in that, If the maximum duration of the RAR window is less than or equal to the length of an H-SFN, then M = ceiling(duration of the RAR window / Tmin_1); If the maximum duration of the RAR window is greater than the length of an H-SFN, then M = ceiling(length of an H-SFN / Tmin_1).

30. The method according to claim 22 or 23, characterized in that, The first message is Msg3, and the first RNTI is determined based on at least one of the following: The identifier of the first SFN corresponding to the Physical Uplink Shared Channel (PUSCH) resource used by Msg3; The identifier of the first H-SFN corresponding to the PUSCH resource used by Msg3; The minimum period supported by the PUSCH resource; The duration of the race condition timer; The identifier of the carrier used by Msg3; The identifier of the subcarrier used by Msg3.

31. The method according to claim 30, characterized in that, When the maximum duration of the contention resolution timer is less than or equal to the length of an H-SFN, The first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + M*carrier_id_2; or, The first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id; Wherein, SFN_id_2 is the identifier of the first SFN corresponding to the PUSCH resource used to transmit Msg3; Tmin_2 is the minimum period supported by the PUSCH resource; N and M are predefined values; subcarrier_id is the identifier of the subcarrier used to transmit Msg3; and carrier_id_2 is the identifier of the carrier used to transmit Msg3.

32. The method according to claim 30 or 31, characterized in that, When the maximum duration of the contention resolution timer is greater than the length of an H-SFN, The first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + P*carrier_id_2 + K2*(H-SFN_id_2mod L2); or, The first RNTI = 1 + floor(SFN_id_2 / Tmin_2) + N*subcarrier_id + P*(H-SFN_id_2mod L2); Wherein, SFN_id_2 is the identifier of the first SFN corresponding to the PUSCH resource used to transmit Msg3; H-SFN_id_2 is the identifier of the first H-SFN corresponding to the PUSCH resource used to transmit Msg3; Tmin_2 is the minimum period supported by the PUSCH resource; N, P, K2, and L2 are all predefined values; subcarrier_id is the identifier of the subcarrier used to transmit Msg3; and carrier_id_2 is the identifier of the carrier used to transmit Msg3.

33. The method according to claim 32, characterized in that, K2 is related to the maximum number of carriers supported by transmitting Msg3.

34. The method according to claim 32 or 33, characterized in that, L2 is the maximum duration of the contention resolution timer.

35. The method according to any one of claims 22 to 34, characterized in that, The method further includes: A second message is sent based on the first RNTI, and the second message is a response message corresponding to the first message.

36. The method according to any one of claims 22 to 35, characterized in that, The period of the transmission resource corresponding to the first message is an integer multiple of the first duration.

37. The method according to claim 36, characterized in that, The first duration is 90ms or 9 wireless frames.

38. A wireless communication method, characterized in that, The method is performed by a terminal device in a non-terrestrial network (NTN) time-division duplex (TDD) system, and the method includes: On the available downlink time domain units within the time interval of the first channel or signal transmission, the physical downlink control channel (PDCCH) is not monitored.

39. The method according to claim 38, characterized in that, The first channel or signal is a first uplink channel or signal, and the transmission of the first uplink channel or signal is distributed in multiple uplink time domain units; The provision that the PDCCH is not monitored on available downlink time domain units within the time interval of the first channel or signal transmission includes: On the available downlink time domain units located between the plurality of uplink time domain units, the PDCCH is not monitored.

40. The method according to claim 39, characterized in that, The first uplink channel or signal is the Physical Uplink Shared Channel (PUSCH) or the Physical Random Access Channel (PRACH).

41. The method according to claim 38, characterized in that, The first channel or signal is a first downlink channel or signal, and the transmission of the first downlink channel or signal is distributed in multiple downlink time domain units; The provision that the PDCCH is not monitored on available downlink time domain units within the time interval of the first channel or signal transmission includes: On the available downlink time domain units located between the plurality of downlink time domain units, the PDCCH is not monitored.

42. The method according to claim 41, characterized in that, The first downlink channel or signal is the Physical Downlink Shared Channel (PDSCH).

43. The method according to any one of claims 38 to 42, characterized in that, The method further includes: If the start time of the non-continuous reception DRX continuous timer is within the first time period, the DRX continuous timer will not be started. Wherein, the first time period is any consecutive time period occupied by the first channel or signal transmission.

44. The method according to any one of claims 38 to 43, characterized in that, The time-domain unit is a subframe or a time slot.

45. A wireless communication method, characterized in that, The method is performed by a network device in a non-terrestrial network (NTN) time-division duplex (TDD) system, and the method includes: The Physical Downlink Control Channel (PDCCH) is not transmitted on the available downlink time domain units within the time interval of the first channel or signal transmission.

46. ​​The method according to claim 45, characterized in that, The first channel or signal is a first uplink channel or signal, and the transmission of the first uplink channel or signal is distributed in multiple uplink time domain units; The provision of not transmitting PDCCH on available downlink time domain units within the time interval of the first channel or signal transmission includes: No PDCCH is transmitted on the available downlink time domain units located between the plurality of uplink time domain units.

47. The method according to claim 46, characterized in that, The first uplink channel or signal is the Physical Uplink Shared Channel (PUSCH) or the Physical Random Access Channel (PRACH).

48. The method according to claim 45, characterized in that, The first channel or signal is a first downlink channel or signal, and the transmission of the first downlink channel or signal is distributed in multiple downlink time domain units; The provision of not transmitting PDCCH on available downlink time domain units within the time interval of the first channel or signal transmission includes: No PDCCH is transmitted on the available downlink time domain units located between the plurality of downlink time domain units.

49. The method according to claim 48, characterized in that, The first downlink channel or signal is the Physical Downlink Shared Channel (PDSCH).

50. The method according to any one of claims 45 to 49, characterized in that, The time-domain unit is a subframe or a time slot.

51. A wireless communication device, characterized in that, The device includes: a transmitting module and a processing module; The sending module is used to send the first message; The processing module is used to calculate the first wireless network temporary identifier (RNTI) based on the time-frequency resources used by the first message.

52. A wireless communication device, characterized in that, The device includes: a receiving module and a processing module; The receiving module is used to receive the first message; The processing module is used to calculate the first wireless network temporary identifier (RNTI) based on the time-frequency resources used by the first message.

53. A wireless communication device, characterized in that, The device includes: a receiving module; The receiving module is configured not to listen to the Physical Downlink Control Channel (PDCCH) on available downlink time-domain units within the time interval of the first channel or signal transmission.

54. A wireless communication device, characterized in that, The device includes: a transmitting module; The transmitting module is configured not to transmit the Physical Downlink Control Channel (PDCCH) on available downlink time domain units within the time interval of the first channel or signal transmission.

55. A communication device, characterized in that, The communication device includes a processor and a memory, the memory storing a computer program, the processor executing the computer program to implement the method as claimed in any one of claims 1 to 21, or to implement the method as claimed in any one of claims 22 to 37, or to implement the method as claimed in any one of claims 38 to 44, or to implement the method as claimed in any one of claims 45 to 50.

56. A computer-readable storage medium, characterized in that, The storage medium stores a computer program that is executed by a processor to implement the method as claimed in any one of claims 1 to 21, or the method as claimed in any one of claims 22 to 37, or the method as claimed in any one of claims 38 to 44, or the method as claimed in any one of claims 45 to 50.

57. A chip, characterized in that, The chip includes programmable logic circuitry and / or program instructions, which, when the chip is running, are used to implement the method as described in any one of claims 1 to 21, or the method as described in any one of claims 22 to 37, or the method as described in any one of claims 38 to 44, or the method as described in any one of claims 45 to 50.

58. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium, which a processor reads from and executes to implement the method as claimed in any one of claims 1 to 21, or the method as claimed in any one of claims 22 to 37, or the method as claimed in any one of claims 38 to 44, or the method as claimed in any one of claims 45 to 50.

Images