Wireless communication method and apparatus, and device and storage medium

Abstract

A wireless communication method and apparatus, and a device and a storage medium, which relate to the technical field of communications. The method comprises: in a CB-CG transmission process, a terminal device sending N PUSCHs, wherein N is an integer greater than 1 (710); and the terminal device starting at least one first timer on the basis of the N PUSCHs (720). In the method, the manner in which the terminal device tests downlink information from a network device is adjusted by means of sending the PUSCHs and starting the first timer, so that the terminal device monitors a response of the network device to any PUSCH as much as possible, thereby reducing the likelihood of missing the response of the network device to the PUSCH.

Description

Wireless communication methods, apparatus, devices 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, and storage medium. Background Technology

[0002] In many scenarios in the field of communication technology, multiple copies of the same data are transmitted to improve the reliability and anti-interference capability of data transmission.

[0003] In related technologies, network devices reserve dedicated transmission resources for specific terminal devices through Configured Grant (CG). When a specific terminal device does not use the transmission resource for periodic services, this leads to a waste of those resources. However, allowing multiple terminal devices to use the same transmission resource can cause transmission conflicts between them. Therefore, the communication technology field has begun to explore contention-based configured grant transmission, where terminal devices use multiple copies of the same data for transmission to reduce the probability of conflicts.

[0004] However, after introducing contention-based configuration authorization transmission, how terminal devices should listen to the responses of network devices still needs further discussion and research.

[0005] Summary of the Invention

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

[0007] According to one aspect of the embodiments of this application, a wireless communication method is provided, the method being executed by a terminal device, the method comprising:

[0008] During CB-CG (contention-based CG) transmission, N PUSCH (Physical Uplink Shared Channel) messages are sent, where N is an integer greater than 1.

[0009] Based on the N PUSCH, start at least one first timer.

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

[0011] The sending module is used to send N PUSCHs during CB-CG transmission, where N is an integer greater than 1;

[0012] The processing module is used to start at least one first timer based on the N PUSCHs.

[0013] According to one aspect of the embodiments of this application, a terminal device is provided, the terminal 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.

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

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

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

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

[0018] By sending a PUSCH, the terminal device starts the first timer and adjusts the way it detects downlink information from the network device. This allows the terminal device to detect the network device's response to any PUSCH as much as possible, reducing the possibility of missing the network device's response to a PUSCH. Attached Figure Description

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

[0020] Figure 2 is a schematic diagram of a discontinuous reception mechanism provided in an embodiment of this application;

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

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

[0023] Figure 5 is a flowchart of the EDT under the user plane transport scheme provided in an embodiment of this application;

[0024] Figure 6 is a schematic diagram of data packet transmission within a TDMA RA frame according to an embodiment of this application;

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

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

[0027] Figure 9 is a schematic diagram of the structure of a terminal device provided in an embodiment of this application. Detailed Implementation

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

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

[0030] 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 (NR) system, evolution 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 (Beyound 5G) systems, 6th-Generation (6G) systems, or other communication systems.

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

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

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

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

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

[0036] 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 device. 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 function, 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 to these. 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 device can also be simply referred to as terminal or UE, the meaning of which will be understood by those skilled in the art.

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

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

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

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

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

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

[0043] I. Background Information on NTN (Non-Terrestrial Network)

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

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

[0046] 1. Low Earth Orbit Satellites

[0047] The LEO altitude range is 500km to 1500km, with a corresponding orbital period 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 the transmission power of terminal equipment are not high.

[0048] 2. Geosynchronous orbit satellite

[0049] The GEO orbit is at an altitude of 35,786 km and has a rotation period of 24 hours around the Earth. The signal propagation delay for single-hop communication between users is typically 250 ms.

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

[0051] II. Configured Grant (CG)

[0052] To better serve cyclical business, the concept of pre-configured resources was introduced, referred to as semi-persistent scheduling (SPS) in the downlink and configuration authorization in the uplink.

[0053] NR supports the following two types of uplink configuration-authorized transports:

[0054] 1. PUSCH transport based on Configured Grant Type 1

[0055] The network's Radio Resource Control (RRC) configures all transmission resources and parameters, including time-domain resources, frequency-domain resources, the period of time-domain resources, the Modulation and Coding Scheme (MCS), repetition count, frequency hopping, and the number of HARQ (Hybrid Automatic Repeat reQuest) processes. Upon receiving this RRC configuration, the terminal can immediately use the configured transmission parameters to perform PUSCH transmission on the configured time-frequency resources.

[0056] 2. PUSCH transport based on Configured Grant Type 2

[0057] A two-step resource configuration approach is adopted: First, the network RRC configures transmission resources and parameters, including the period, repetition count, frequency hopping, and HARQ process count for time-domain resources. Then, a second type of configuration-based PUSCH transmission is activated using a PDCCH (Physical Downlink Control Channel) scrambled with CS-RNTI (Configured Scheduling-Radio Network Temporary Identifier), simultaneously configuring other transmission resources and parameters, including time-domain resources, frequency-domain resources, and MCS. Upon receiving the RRC configuration parameters, the terminal device cannot immediately use the configured resources and parameters for PUSCH transmission; it must wait until it receives the corresponding PDCCH activation and configures other resources and parameters before it can perform PUSCH transmission.

[0058] Since the maximum number of HARQ processes for a terminal device is 16, the network device configures a limited number of HARQ process IDs for each CG configuration. The terminal device uses these HARQ process IDs in a round-robin manner for uplink transmission on the CG resource. Assuming that the HARQ process ID of the CG resource at time t0 and the HARQ process ID of the CG resource at time t1 are both HARQ ID i, when the terminal device assembles MAC PDU (Media Access Control Protocol Data Unit) 1 at time t0, it stores MAC PDU1 in HARQ ID i. At time t1, since it uses the same HARQ process as at time t0, MAC PDU1 will be flushed, even if it has not yet been correctly transmitted. Therefore, a per-HARQ process configuration grant timer (configuredGrantTimer) is introduced. The maintenance method of configuredGrantTimer is as follows:

[0059] If the terminal device performs an uplink transmission on resources scheduled by PDCCH, and the HARQ process used for the uplink transmission is available for configured authorized transmission, the terminal device starts or restarts the configuredGrantTimer corresponding to the HARQ process.

[0060] If the terminal device performs an uplink transmission on the configured authorized resources, the terminal device starts or restarts the configuredGrantTimer corresponding to the HARQ process.

[0061] If the terminal device receives a PDCCH instruction indicating that configured grant Type 2 is activated, the terminal device stops the running configuredGrantTimer.

[0062] The MAC PDU stored in a HARQ process cannot be flushed before the configuredGrantTimer for that HARQ process expires.

[0063] NR-U (NR in unlicensed spectrum) introduces an automatic CG retransmission mechanism, specifically the `cg-RetransmissionTimer` parameter. After each CG transmission, the terminal device starts or restarts the `cg-RetransmissionTimer` for the corresponding HARQ process. If the HARQ process receives downlink feedback or uplink scheduling information, the terminal device stops the timer. If the process's `configuredGrantTimer` times out, the terminal device also stops the timer. If `configuredGrantTimer` is still running after `cg-RetransmissionTimer` times out, CG resources are used for retransmission.

[0064] III. 5G NR DRX (Discontinuous Reception) Process

[0065] In 5G NR, network devices can configure DRX functionality for terminal devices, enabling them to listen to the PDCCH discontinuously, thereby saving power. Each MAC entity has one DRX configuration, and the DRX configuration parameters include:

[0066] -drx-onDurationTimer: the duration at the beginning of a DRX cycle; (DRX duration timer: the duration after the start of a DRX cycle)

[0067] -drx-SlotOffset: the delay before starting the drx-onDurationTimer; (DRX slot offset: the delay before starting drx-onDurationTimer)

[0068] -drx-InactivityTimer: the duration after the PDCCH occasion in which a PDCCH indicates a new UL or DL ​​transmission for the MAC entity; (DRX Inactivity Timer: the duration after the PDCCH transmission occasion in which the PDCCH indicates a new uplink or downlink transmission for the MAC entity)

[0069] -drx-RetransmissionTimerDL (per DL HARQ process except for the broadcast process): the maximum duration until a DL retransmission is received; (DRX downlink retransmission timer (per downlink HARQ process except for the broadcast process): the maximum duration until a downlink retransmission is received)

[0070] -drx-RetransmissionTimerUL(per UL HARQ process): the maximum duration until a grant for UL retransmission is received; (DRX uplink retransmission timer (per uplink HARQ process): the maximum duration for receiving an uplink authorized retransmission)

[0071] -drx-LongCycleStartOffset: The Long DRX cycle and drx-StartOffset, which define the subframe where the Long and Short DRX cycles start.

[0072] -drx-ShortCycle (optional): the Short DRX cycle;

[0073] -drx-ShortCycleTimer (optional): The duration the UE shall follow the Short DRX cycle; (DRX Short Cycle Timer (optional): The terminal device shall follow the duration of the Short DRX cycle)

[0074] -drx-HARQ-RTT-TimerDL (per DL HARQ process except for the broadcast process): the minimum duration expected by the MAC entity before a DL assignment for HARQ retransmission; (DRX-HARQ-RTT (Routine-Trip Time) - downlink timer (per downlink HARQ process except for the broadcast process): the minimum duration predicted by the MAC entity before a downlink configuration for HARQ retransmission).

[0075] -drx-HARQ-RTT-TimerUL (per UL HARQ process): the minimum duration before a UL HARQ retransmission grant is expected by the MAC entity. (DRX-HARQ-RTT-Uplink Timer: The minimum duration predicted by the MAC entity before an uplink configuration for HARQ retransmission.)

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

[0077] Any one of the following five timers is running: -drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-RetransmissionTimerUL, and ra-ContentionResolutionTimer.

[0078] - An SR (Scheduling Request) was sent on the PUCCH and is currently in a pending state.

[0079] - In a contention-based random access process, the terminal device has not yet received an initial transmission of PDCCH scrambled with C-RNTI (Cell-RNTI, Cell-Radio Network Temporary Identifier) ​​after successfully receiving the random access response.

[0080] As shown in Figure 2, the terminal device 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:

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

[0082] 1> If Long DRX Cycle is used, and the current subframe satisfies [(SFN×10)+subframe number]modulo(drx-LongCycle)=drx-StartOffset:

[0083] 2> Start drx-onDurationTimer at a time after drx-SlotOffset slots from the start of the current subframe.

[0084] The conditions for the terminal to start or restart drx-InactivityTimer are:

[0085] If the terminal receives a PDCCH indicating the initial downlink or uplink transmission, the terminal starts or restarts the drx-InactivityTimer.

[0086] The conditions for starting and stopping drx-RetransmissionTimerDL on a terminal device are as follows:

[0087] When the terminal device receives a PDCCH indicating downlink transmission, or when the terminal device receives a MAC PDU on the configured downlink licensed resources, the terminal device stops the drx-RetransmissionTimerDL corresponding to the HARQ process. After completing the transmission of the HARQ process feedback for this downlink transmission, the terminal device starts the drx-HARQ-RTT-TimerDL corresponding to the HARQ process.

[0088] If the timer drx-HARQ-RTT-TimerDL corresponding to a certain HARQ on the terminal device times out, and the downlink data transmitted using this HARQ process fails to be decoded, then the terminal device starts the drx-RetransmissionTimerDL corresponding to this HARQ process.

[0089] The conditions for starting and stopping drx-RetransmissionTimerUL on the terminal device are as follows:

[0090] When the terminal device receives a PDCCH indicating uplink transmission, or when the terminal device sends a MAC PDU on the configured uplink grant resource, the terminal device stops the drx-RetransmissionTimerUL corresponding to the HARQ process. After completing the first repetition of this PUSCH, the terminal device starts the drx-HARQ-RTT-TimerUL corresponding to the HARQ process.

[0091] If the timer drx-HARQ-RTT-TimerUL corresponding to a certain HARQ on the terminal device times out, the terminal device will start the drx-RetransmissionTimerUL corresponding to this HARQ process.

[0092] As can be seen from the DRX process above, after completing uplink transmission or HARQ process feedback for downlink transmission, the terminal device first starts a DRX HARQ RTT timer (drx-HARQ-RTT-TimerUL for uplink transmission and drx-HARQ-RTT-TimerDL for downlink transmission). During the execution of this DRX HARQ RTT timer, the terminal device remains in a sleep state and does not listen to the PDCCH. Only after the timer expires does the terminal device begin listening for uplink retransmission scheduling or determine whether to begin listening for downlink retransmission scheduling based on the feedback. drx-HARQ-RTT-TimerUL and drx-HARQ-RTT-TimerDL are semi-statically configured by the network device's RRC.

[0093] In NTN, considering the propagation delay from terminal equipment to network equipment, drx-HARQ-RTT-TimerUL and drx-HARQ-RTT-TimerDL in the above DRX process are replaced with HARQ-RTT-TimerUL-NTN and HARQ-RTT-TimerDL-NTN. The only difference is that the latter adds a UE-gNB RTT (UE-gNB Routine-Trip Time, UE-gNB round-trip delay) to the parameter values ​​of the former.

[0094] IV. LTE Random Access Procedure

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

[0096] 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);

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

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

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

[0100] 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).

[0101] 6. SR failed;

[0102] 7. Synchronous reconfiguration request from RRC.

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

[0104] Figure 3 illustrates a contention-based random access method, characterized by code resource sharing and a four-step access process: access request, access response, connection request, and conflict resolution. This process includes 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.

[0105] Step 1: Access Request (The terminal device sends Msg1 to the network)

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

[0107] Step 2: Access Response (Network device sends Msg2 to terminal device)

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

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

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

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

[0112] In the NR system, RA-RNTI is calculated as follows:

[0113] RA-RNTI=1+s_id+14×t_id+14×80×f_id+14×80×8×ul_carrier_id

[0114] Wherein, s_id is the index of the first OFDM (Orthogonal Frequency Division Multiplexing) symbol of the PRACH timing (0≤s_id≤14), t_id is the index of the first slot of the PRACH timing in the system frame (0≤t_id≤80), f_id is the index of the PRACH timing in the frequency domain (0≤f_id≤8), and ul_carrier_id is the UL carrier used for random access preamble transmission (0 represents NUL (Normal Uplink) carrier, and 1 represents SUL (Supplementary Uplink) carrier).

[0115] For eMTC (enhanced Machine-Type Communication) UEs, RA-RNTI is calculated as follows:

[0116] RA-RNTI=1+t_id+10*f_id+60*(SFN_id mod(Wmax / 10))

[0117] Where 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 Number) of PRACH transmission, and Wmax is the maximum RAR window length supported by eMTC, which is 400 subframes.

[0118] For NB-IoT UEs, RA-RNTI is calculated as follows:

[0119] RA-RNTI=1+floor(SFN_id / 4)+256*carrier_id

[0120] Here, SFN_id is the index of the first SFN transmitted via PRACH, and carrier_id is the index of the UL carrier corresponding to the PRACH transmission. The carrier_id corresponding to the Anchor carrier is 0.

[0121] For NB-IoT UEs in TDD (Time Division Duplexing) mode, RA-RNTI is calculated as follows:

[0122] RA-RNTI=1+floor(SFN_id / 4)+256*(H-SFN mod 2)

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

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

[0125] 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 the RAR. The RAR specifically contains the following information:

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

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

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

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

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

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

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

[0133] Step 3: Connection Request (The terminal device transmits Msg3 on network scheduling resources)

[0134] Msg3 is the Scheduled Transmission. 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 (UE identifier) ​​and establishment cause; if it's an RRC reconstruction, it will carry the connected state UE ID and establishment cause. Furthermore, the ID carried in Msg3 allows contention to be resolved in Step 4.

[0135] Step 4: Conflict resolution (Network device sends Msg4 to terminal device)

[0136] Msg4 stands for Contention Resolution. Msg4 serves two purposes: first, it resolves contention conflicts; second, it enables network devices to transmit RRC configuration messages to end devices.

[0137] There are two methods for resolving contention conflicts: 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.

[0138] Figure 4 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 steps Step 0 through 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 through Msg2.

[0139] Step 0: Leader assignment (Msg0)

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

[0141] Step 1: Access Request (Network terminal sends Msg1 to the network)

[0142] Step 2: Access Response (Network device sends Msg2 to terminal device)

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

[0144] 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 random access preamble based on the RACH time-frequency resources used by the random access preamble received from the terminal device. Therefore, the network device determines the initial TA (Timing Advance) of the terminal device based on the transmission and reception times of the random access preamble, and informs the terminal device through the RAR.

[0145] V. EDT (Early Data Transmission)

[0146] In traditional LTE systems, if a terminal device in RRC IDLE state needs to transmit uplink data, it must first initiate an RRC connection establishment process through a random access procedure. Only after establishing an RRC connection with the network device can it transmit data. To reduce signaling interactions between the terminal device and the network device during data transmission and to save terminal power consumption, the EDT mechanism is introduced for NB-IoT and eMTC. This feature allows a terminal device in RRC IDLE state to transmit UL data via Msg3 during the random access procedure. Upon receiving a successful reception response from the network device, the random access procedure terminates, and the terminal device remains in RRC IDLE state without entering RRC connected state. The network device configures a separate NPRAC (Narrowband Physical Random Access Channel) resource for EDT. When the amount of UL data to be transmitted by the terminal device does not exceed the data limit configured by the network device, the terminal device can send Msg1 on the separate NPRACH resource of EDT to request Msg3 authorization from the network device for EDT. Figure 5 shows a flowchart of the EDT (Electronic Access Deployment) scheme under the user plane transmission scheme. In Figure 5, after the terminal device sends a random access preamble to the network device and receives the random access response from the network device, the following process begins:

[0147] 1. The terminal device sends an RRC connection resume request and uplink data to the network device. The RRC connection resume request carries a resume ID, a resume cause, and a short resume message authentication code for integrity (MAC-I).

[0148] 2. The network device sends a Context Resume Request in the S1-AP (S1 Application Protocol) protocol to the Mobility Management Entity (MME);

[0149] 3. Modify the bearer between the mobility management device and the serving gateway (S-GW);

[0150] 4. The mobility management device sends a Context Resume Response (S1-AP protocol) to the network device.

[0151] 5. The network device sends uplink data to the serving gateway;

[0152] 6. The service gateway sends downlink data to the network devices;

[0153] 7. Suspend the S1 interface between the network device and the mobility management entity; modify the bearer between the mobility management device and the service gateway;

[0154] 8. The network device sends an RRC connection release message and downlink data to the terminal device. The RRC connection release message carries the release cause, recovery identifier and network color code (NCC).

[0155] Currently, CG (Current Access Control) resources are reserved for specific terminal devices, ensuring that there are no transmission conflicts from other terminal devices during CG transmission. CG resources are configured and repeated periodically, making them well-suited for periodic services such as VoIP (Voice over Internet Protocol). When CG is used for non-periodic service transmission, some CG opportunities may be wasted due to a lack of uplink traffic. Since these CG resources are reserved for the specific UE (User Equipment), they cannot be used by other UEs. To improve resource utilization and uplink capacity, a contention-based CG transmission method needs to be considered.

[0156] In some current satellite communication standards, DSA (Diversity Slotted ALOHA) or CRDSA (Contention Resolution Diversity Slotted ALOHA) is used to effectively improve the utilization of random access resources and reduce the probability of collisions between different terminal devices. Taking Msg3 transmission as an example, the basic idea of ​​DSA is that the terminal device uses different Msg3 transmission resources to send multiple copies of Msg3. As long as the network device can successfully receive one of the Msg3s, the UE can consider the EDT (Electronic Data Transfer) to be successful. Thus, DSA increases the probability that the terminal device's Msg3 will be successfully received by the base station by increasing the Msg3 transmission opportunities, thereby improving system capacity. CRDSA is a further enhancement of DSA. The terminal device uses different Msg3 transmission resources to send multiple copies of Msg3. The network device stores all received data within a complete frame and uses interference cancellation technology to enable the network device to successfully receive Msg3s sent by more terminal devices. Figure 3 illustrates the packet transmission within a frame. Each rectangle represents a packet transmission; rectangles filled with the same lines indicate packets sent by the same UE, while rectangles filled with different lines indicate packets sent by different UEs. The numbers on the rectangles indicate the UE that sent the packet; for example, a rectangle with the number 1 indicates that the packet was sent by UE1. In Figure 6, each packet has two copies. That is, each UE sends two Msg3 copies using different Msg3 transmissions. Figure 6 includes six UEs (UE1, UE2, UE3, UE4, UE5, and UE6), each sending two packets. The base station can demodulate the packets sent by these six UEs sequentially: UE3 -> UE2 (by eliminating UE3's packet) -> UE1 (by eliminating UE2's packet) -> UE6 (by eliminating UE1's packet). Finally, only the packets from UE4 and UE5 cannot resolve their conflicts.

[0157] When DSA / CRDSA is used for connected-mode CG transmission, it is necessary to solve problems such as how to transmit, how to perform network device response monitoring, how to solve automatic retransmission, and how to determine if CG transmission is successful.

[0158] Please refer to Figure 7, which shows a flowchart of a wireless communication method provided in one embodiment of this application. The method is performed by a terminal device and can be applied to the network architecture shown in Figure 1. The method includes at least one of the following steps 710 and 720.

[0159] Step 710: During the CB-CG transmission process, the terminal device sends N PUSCHs, where N is an integer greater than 1.

[0160] CB-CG refers to a transmission method in which multiple terminal devices compete for the same CG resource for uplink transmission. In some embodiments, the first terminal device among the multiple terminal devices successfully competes for the resource, meaning the first terminal device successfully uses the CG resource for uplink transmission. The first terminal device can be any one of the multiple terminal devices. CB-CG resources refer to a set of resources pre-configured by the network device for multiple terminal devices, used for uplink transmission.

[0161] In some embodiments, the terminal device sends N PUSCHs to the network device. Sending a PUSCH means that the terminal device transmits uplink data through the PUSCH. The uplink data can be any uplink data sent by the terminal device to the network device. The uplink data is sent in multiple copies.

[0162] In some embodiments, uplink data is carried on the PUSCH. In some embodiments, a copy of the uplink data is carried on the PUSCH. In some embodiments, each of the N PUSCHs corresponds to different transmission resources. These transmission resources include time-domain resources and / or frequency-domain resources.

[0163] In some embodiments, CB-CG resources are configured by a network device. In some embodiments, the network device can broadcast pre-configuration information to multiple terminal devices to configure CB-CG resources. For example, CB-CG resources can be configured for multiple terminal devices via system information. In some embodiments, the network device can also configure CB-CG resources for multiple terminal devices via RRC configuration messages, where the RRC configuration messages carry pre-configuration information.

[0164] In some embodiments, before the terminal device sends N PUSCHs, the terminal device receives pre-configuration information sent by the network device, which includes CB-CG resource configuration information. The CB-CG resource configuration information is used to indicate the pre-configured CB-CG resources, including time-domain resources and frequency-domain resources.

[0165] In some embodiments, CB-CG resource configuration information indicates multiple CB-CG resource groups configured by the network device. Each CB-CG resource group includes transport resources for at least one PUSCH.

[0166] In some embodiments, the terminal device selects a target CB-CG resource group from multiple CB-CG resource groups, where each CB-CG resource group contains multiple CB-CG transmission opportunities. The terminal device then randomly selects N CB-CG transmission opportunities from the multiple CB-CG transmission opportunities contained in the target CB-CG resource group to send PUSCH.

[0167] In some embodiments, the terminal device randomly selects one CB-CG resource group from multiple CB-CG resource groups as the target CB-CG resource group. In some embodiments, the number of CB-CG transmission opportunities included in different CB-CG resource groups may be the same or different. For example, the number of CB-CG transmission opportunities included in each CB-CG resource group is Nmax, where Nmax is the maximum number of CB-CG transmission opportunities included in the CB-CG resource group, and Nmax is an integer greater than 1.

[0168] In some embodiments, a CB-CG resource group is determined based on at least one of the following: a time window, a time-domain start position, a maximum number of transmission opportunities, a period, and an offset. A time window, also called a time period, refers to a time interval corresponding to a CB-CG resource group. Multiple CB-CG transmission opportunities contained in a CB-CG resource group are determined within their corresponding time windows. Understandably, the time windows of any two CB-CG resource groups do not overlap. The time-domain start position can be the start position of the time-domain resource corresponding to the first CB-CG transmission opportunity in the CB-CG resource group. The maximum number of CB-CG transmission opportunities refers to the maximum number of CB-CG transmission opportunities contained in the CB-CG resource group. The period refers to the time interval between the time-domain start position of an adjacent CB-CG resource group and the time-domain start position of the adjacent CB-CG resource group. The offset can be the time interval between the time-domain start position of the first CB-CG resource group and the time interval between a specified CB-CG transmission opportunity within the same CB-CG resource group and the first CB-CG transmission opportunity.

[0169] CB-CG transmission timing refers to the time-frequency resources used by the terminal device when sending PUSCH. Understandably, the selected N CB-CG transmission timings correspond to different time-domain and / or frequency-domain resources.

[0170] In some embodiments, the PUSCH carries first information, which indicates the transmission timing of each of the N PUSCHs. In some embodiments, the first information may include identification information of the CB-CG transmission timing of each of the N PUSCHs. Optionally, when the network device determines the multiple CB-CG transmission timings included in the CB-CG resource group, it assigns identification information to each of the multiple CB-CG transmission timings. In some embodiments, the first information may be range information of the CB-CG transmission timings, which indicates the CB-CG transmission timings within a specified range in the CB-CG resource group.

[0171] In some embodiments, any two PUSCHs among the N PUSCHs may contain the same or different content. In some embodiments, when any two PUSCHs among the N PUSCHs contain different content, the content contained in the N PUSCHs is related to each other. For example, when the amount of first uplink data that the terminal device needs to transmit is large, a fragmented transmission method is used to transmit a portion of the first uplink data using N PUSCHs respectively. Therefore, after receiving the N PUSCHs, the network device can reassemble the first uplink data according to the first information contained in the PUSCHs.

[0172] In the above method, by carrying first information in the PUSCH, the network device can determine other PUSCHs associated with the received PUSCH based on the first information.

[0173] In some embodiments, the number of PUSCHs is configured by the network device or determined by the terminal device based on the maximum number configured by the network device.

[0174] In some embodiments, where the number of PUSCHs is configured by the network device, the network device can configure the number of PUSCHs that the terminal device will send via RRC configuration messages or broadcasts.

[0175] In some embodiments, where the number of PUSCHs is determined by the terminal device based on the maximum number configured by the network device, the number of PUSCHs is less than or equal to the maximum number configured by the network device. The maximum number configured by the network device refers to the maximum number of transmission opportunities Nmax contained in the resource group.

[0176] In some embodiments, the number of PUSCHs may also be specified by the relevant protocol, which is not limited in this application.

[0177] In some embodiments, the above N PUSCHs use the same HARQ process.

[0178] In some embodiments, the CG resource configuration information further includes second information, which indicates the M HARQ processes configured by the network device, where M is an integer greater than or equal to 1 and less than or equal to 16. In some embodiments, the terminal device uses the M HARQ processes in a polling manner. N PUSCH processes using the same HARQ process means that these N HARQ processes also share the buffer of the same HARQ process.

[0179] Step 720: Based on N PUSCH, start at least one first timer.

[0180] The first timer is used to put the terminal device into a sleep state for a specified time interval, which is the duration of the first timer. The sleep state of the terminal device, also known as a low-power state, is when the terminal device does not listen to the downlink channel. In some embodiments, the terminal device starts listening to the downlink channel after the first timer expires. In some embodiments, the downlink channel is the PDCCH. In some embodiments, the first timer is a DRX-HARQ-RTT timer. In some embodiments, the first timer is a HARQ-RTT-TimerUL-NTN. After the first timer starts, if no event occurs that interrupts the first timer, the first timer will continue running until its running time equals the duration of the first timer.

[0181] In some embodiments, the way the first timer is started or restarted during CB-CG transmission differs for DSA and CRDSA, and this will be explained in detail below.

[0182] (I) CB-CG transmission process based on DSA

[0183] During DSA-based CB-CG transmission, the terminal device randomly selects N CB-CG transmission opportunities from the target CB-CG resource group and sends N PUSCHs respectively. Where N is less than or equal to Nmax.

[0184] In some embodiments, when the CB-CG transmission process is a DSA-based CB-CG transmission process, the content contained in the N PUSCHs may be the same or different. The content contained in the PUSCH refers to the payload corresponding to the PUSCH. The payload refers to the effective data portion actually carried in the PUSCH, that is, the uplink data that the PUSCH needs to carry.

[0185] When N PUSCHs contain identical content, sending N PUSCHs with the same content at N randomly selected CB-CG transmission times can improve the success rate and reliability of uplink data transmission. Even if the aforementioned N PUSCHs fail due to collisions or interference, the uplink data is considered to have been successfully transmitted as long as at least one PUSCH is successfully received.

[0186] When the contents of the N PUSCHs are different, each of the aforementioned N PUSCHs can carry a portion of the uplink data to be transmitted. This method enables data fragmentation and reassembly, thereby allowing the transmission of larger amounts of uplink data.

[0187] In some embodiments, a first timer is started upon completion of each PUSCH transmission. In some embodiments, each PUSCH corresponds to one first timer. That is, the terminal device starts a corresponding first timer each time it sends a PUSCH. Therefore, the start time of each first timer is the moment a PUSCH transmission is completed. Since the start time of the first timer is independent of the other first timers, the terminal device can maintain a maximum of N first timers for the same HARQ process.

[0188] In some embodiments, the duration of at least one first timer may be the same or different, and this application embodiment does not limit this. In some embodiments, the duration of at least one first timer may be configured by the network device or determined based on the configuration of the network device, and this application embodiment does not limit this.

[0189] In some embodiments, for each first timer, a second timer is started after the first timer expires. That is, the terminal device starts the second timer corresponding to the expired first timer when any first timer expires. One first timer corresponds to one second timer; therefore, the terminal device can maintain a maximum of N second timers.

[0190] The second timer instructs the terminal device to listen to the downlink channel within a specified time interval, where the specified time interval is the duration of the second timer. In some embodiments, during the operation of the second timer, the terminal device detects downlink information from the network device. After the second timer starts, if no event occurs that would interrupt it, the second timer will continue running until its duration equals the timer's duration. In some embodiments, the second timer is a Retransmission Timer. In some embodiments, the second timer is a drx-Retransmission Timer UL.

[0191] In some embodiments, the duration of the first timer is at least less than or equal to the round-trip time between the terminal device and the network device. This is because it is necessary to ensure that the second timer starts in a timely manner to ensure that the network device's response to PUSCH is not missed. In some embodiments, the duration of the first timer plus the duration of the second timer is at least greater than or equal to the round-trip time between the terminal device and the network device.

[0192] In some embodiments, during the execution of the target second timer, if the terminal device receives a new transmission or retransmission of the HARQ process used by the network device to schedule the PUSCH, or if the network device indicates that the PUSCH reception was successful, at least one of the following operations is performed for the first timer or the second timer:

[0193] (1) Stop the target's second timer;

[0194] (2) Stop the first timer that has been started or is about to be started;

[0195] (3) Stop the second timer that has already started or is about to start;

[0196] (4) Stop sending PUSCH from the CB-CG resource group used by PUSCH, and stop sending PUSCH from the CB-CG transmission timing selected but not yet transmitted.

[0197] The target second timer can be any second timer.

[0198] In some embodiments, during the execution of the target second timer, the terminal device receives downlink information from the network device. The downlink information is a response from the network device to at least one PUSCH that has been sent.

[0199] In some embodiments, downlink information is used to indicate a new transmission of the HARQ process used to schedule the PUSCH. Here, "new transmission" refers to the terminal device transmitting a new PUSCH. The HARQ process used for this new PUSCH is the same as the HARQ process used for the PUSCH corresponding to the target second timer. In some embodiments, the new PUSCH is the next PUSCH to be transmitted. In this case, the terminal device performs operations (1) to (4) to transmit the next PUSCH.

[0200] In some embodiments, downlink information is used to instruct the HARQ process using the scheduled PUSCH to retransmit. Here, retransmission means that, for the target second timer, the terminal device retransmits the same content using the corresponding PUSCH. In this case, the terminal device performs operations (1) to (4) to retransmit the PUSCH corresponding to the target second timer.

[0201] In some embodiments, the downlink information indicates that the PUSCH was successfully received. That is, the terminal device successfully competes for CB-CG resources to send the PUSCH. In some embodiments, when the downlink information indicates that the PUSCH was successfully received, and N PUSCHs contain the same content, the terminal device performs operations (1) to (4). This is because the successful reception of a PUSCH by the network device is considered as a successful uplink transmission by the terminal device, and the terminal device does not need to send other PUSCHs containing the same content.

[0202] In some embodiments, when the downlink information indicates that the PUSCH was successfully received and the contents of the N PUSCHs are different, the terminal device performs operation (1). Since the contents of the N PUSCHs are different, the network device only successfully receives one PUSCH and cannot obtain the complete uplink data, so it needs to continue to send or retransmit other PUSCHs.

[0203] In the above method, for the CB-CG transmission process based on DSA, since the terminal device only relies on a single PUSCH transmission to receive data, it is only necessary to start the first timer and the second timer after each PUSCH transmission to ensure that the terminal device has the opportunity to receive the response from the network device after each PUSCH transmission.

[0204] (II) CB-CG transmission process based on CRDSA

[0205] In CRDSA-based CB-CG transmission, the terminal device also randomly selects N CB-CG transmission opportunities from the target CB-CG resource group to send N PUSCHs respectively. However, unlike CRDSA-based CB-CG transmission, in CRDSA-based CB-CG transmission, only the first timer is started once. Compared to DSA-based CB-CG transmission, in CRDSA-based CB-CG transmission, network devices can use Joint Interference Cancellation (JIC) technology to receive the PUSCHs sent by the terminal device, thus resolving collisions and interference issues during PUSCH transmission.

[0206] Joint interference cancellation is a technique used in wireless communication systems to improve signal reception quality and system capacity. This technique improves the signal-to-noise ratio (SNR) of the target signal by coordinating multiple antennas and receivers to process and eliminate interference from other signal sources.

[0207] In some embodiments, when the CB-CG transmission process is a CRDSA-based CB-CG transmission process, the N PUSCHs contain the same content. In some embodiments, after successfully receiving any PUSCH, the network device decodes the received PUSCH. Based on the content contained in the received PUSCH, interference from other conflicting PUSCHs can be eliminated. For example, if PUSCH 1 is successfully decoded in CB-CG transmission moment 1, the network device can use the content of PUSCH 1 to eliminate interference from PUSCH 2 in CB-CG transmission moment 2. Here, PUSCH 2 may be a PUSCH sent by another terminal device. Therefore, when the CB-CG transmission process is a CRDSA-based CB-CG transmission process, for the same terminal device, the N PUSCHs sent should contain the same content.

[0208] In some embodiments, a first timer is started when the earliest PUSCH among the N PUSCHs is transmitted. Understandably, the earliest PUSCH refers to the PUSCH with the earliest CB-CG transmission time among the N PUSCHs, that is, the first PUSCH among the N PUSCHs. Therefore, the terminal device starts the first timer when the first PUSCH among the aforementioned N PUSCHs is transmitted.

[0209] In some embodiments, a second timer is started after the first timer expires. That is, the terminal device starts the second timer when the first timer expires.

[0210] In some embodiments, during the execution of the target second timer, the terminal device receives downlink information from the network device. The downlink information is a response from the network device to at least one PUSCH that has been sent.

[0211] In some embodiments, downlink information is used to instruct the terminal device to retransmit the PUSCH. In this case, the terminal device reselects N CB-CG transmission opportunities and retransmits N PUSCH.

[0212] In some embodiments, downlink information is used to indicate successful PUSCH reception. That is, if the network device successfully receives at least one PUSCH sent by the terminal device during the execution of the first timer, it means that the terminal device has successfully competed for CB-CG resources to send PUSCH.

[0213] In some embodiments, the duration of the first timer is at least less than or equal to the round-trip time between the terminal device and the network device. This is because it is necessary to ensure that the second timer starts in a timely manner to ensure that the network device's response to the first PUSCH is not missed.

[0214] In some embodiments, the duration of the second timer is related to at least one of the following: the timing of the earliest CB-CG transmission used by the PUSCH, the CB-CG resource group used to transmit the PUSCH, and the timing of the last CB-CG transmission in the CB-CG resource group used to transmit the PUSCH.

[0215] The duration of the second timer is at least sufficient to allow the terminal device to receive a response from the network device for any PUSCH. For example, the duration of the second timer could be the delay between the earliest CB-CG transmission time of the PUSCH and the latest CB-CG transmission time of the PUSCH. Alternatively, the duration of the second timer could be the delay between the earliest CB-CG transmission time of the PUSCH and the latest CB-CG transmission time in the CB-CG resource group used for the PUSCH. Or, the duration of the second timer could be the delay between the first CB-CG transmission time in the CB-CG resource group used for the PUSCH and the latest CB-CG transmission time in the CB-CG resource group used for the PUSCH.

[0216] In some embodiments, the duration of the second timer is determined based on the configured duration of the second timer and a first duration, the first duration being related to at least one of the following: the timing of the earliest CB-CG transmission used by the PUSCH, the CB-CG resource group used for transmitting the PUSCH, and the timing of the last CB-CG transmission in the CB-CG resource group used for transmitting the PUSCH.

[0217] The configuration duration of the second timer is the pre-configured initial duration of the second timer. In some embodiments, the configuration duration of the second timer is configured by the network device. For example, the configuration duration of the second timer is configured by the network device via an RRC configuration message. In some embodiments, the configuration duration of the second timer may also be specified by a relevant protocol, which is not limited in this application.

[0218] The first duration is determined based on the PUSCH to be sent by the terminal device. The first duration ensures that the terminal device can receive a response from the network device for any PUSCH during the operation of the second timer. In some embodiments, the duration of the second timer is determined by adding the configured duration of the second timer to the first duration. For example, the first duration plus the configured duration of the second timer is the delay between the earliest CB-CG transmission timing of the PUSCH and the CB-CG transmission timing of the last sent PUSCH. Alternatively, the first duration plus the configured duration of the second timer is the delay between the earliest CB-CG transmission timing of the PUSCH and the last CB-CG transmission timing in the CB-CG resource group used for transmitting the PUSCH. Or, the first duration plus the configured duration of the second timer is the delay between the first CB-CG transmission timing in the CB-CG resource group used for transmitting the PUSCH and the last CB-CG transmission timing in the CB-CG resource group used for transmitting the PUSCH.

[0219] In some embodiments, the duration of the second timer is such that the response from the network device to the last transmitted PUSCH is received. In some embodiments, the configured duration of the second timer is greater than or equal to the sum of the latency between the network device and the terminal device, and the processing latency of the network device for the last transmitted PUSCH.

[0220] In the above method, during CB-CG transmission based on CRDSA, since network devices may use all PUSCH transmissions (from different terminal devices) in the CB-CG resource group to receive PUSCH from each terminal device, the terminal device waiting for the network device's response needs to take into account the timing of the terminal device's last available CB-CG transmission in the CB-CG resource group. Therefore, the duration of the second timer needs to take into account the processing latency of this part of the network device to ensure that the network device's response is not missed.

[0221] In some embodiments, the terminal device receives configuration information, which indicates whether to use joint interference cancellation technology to receive PUSCH.

[0222] In some embodiments, the configuration information is sent by the network device. In some embodiments, the configuration information is used to indicate whether the network device uses joint interference cancellation techniques to receive the first message.

[0223] In some embodiments, the pre-configuration information also includes configuration information. That is, the network device can send CG resource configuration information and configuration information together to the terminal device using the same message.

[0224] In some embodiments, when the configuration information indicates that joint interference cancellation technology is not used to receive PUSCH, the terminal device starts a timer after each PUSCH transmission is completed. That is, when the network device does not use joint interference cancellation technology to receive PUSCH, the terminal device adopts the method of starting at least one first timer corresponding to the DSA-based CB-CG transmission process.

[0225] In some embodiments, the configuration information directly instructs the terminal device to use the method of starting at least one first timer corresponding to the DSA-based CB-CG transmission procedure. Correspondingly, the network device does not use joint interference cancellation techniques to receive PUSCH.

[0226] In some embodiments, when the configuration information indicates that joint interference cancellation technology is used to receive PUSCH, the terminal device starts a first timer when it completes the transmission of the earliest of the N PUSCHs. That is, when the network device uses joint interference cancellation technology to receive PUSCH, the terminal device adopts the method of starting at least one first timer corresponding to the CRDSA-based CB-CG transmission process.

[0227] In some embodiments, the configuration information directly instructs the terminal device to use a method corresponding to the CRDSA-based CB-CG transmission procedure to start at least one first timer. Correspondingly, the network device uses joint interference cancellation techniques to receive the PUSCH.

[0228] The solution provided in this application embodiment involves a terminal device sending a PUSCH to start a first timer and adjusting the terminal device's detection method for downlink information from the network device. This allows the terminal device to monitor the network device's response to any PUSCH as much as possible, reducing the possibility of missing the network device's PUSCH response.

[0229] In some embodiments, the introduction of the CB-CG transmission mode has different effects on the configuration grant timer (CG timer) and the configuration grant-based retransmission timer (CG retransmission timer) for DSA and CRDSA. The following embodiments will classify and explain these effects.

[0230] Scenario 1: The impact on the CG timer in DSA-based CB-CG transmission mode.

[0231] In some embodiments, the CG timer is started after the Nth CB-CG transmission opportunity in the CB-CG resource group used for transmitting PUSCH, and the terminal device considers the CG timer to be running between the first CB-CG transmission opportunity selected by the terminal device and the Nth CB-CG transmission opportunity.

[0232] The CG timer is used to prevent N PUSCHs that a terminal device wants to send within a specified time period from being overwritten by PUSCHs sent by other terminal devices using the same HARQ process. The specified time period is the duration of the CG timer.

[0233] The first CB-CG transmission opportunity selected by the terminal device refers to the earliest CB-CG transmission opportunity among N CB-CG transmission opportunities. Similarly, the Nth CB-CG transmission opportunity selected by the terminal device refers to the latest CB-CG transmission opportunity among N CB-CG transmission opportunities.

[0234] After introducing the DSA-based CB-CG transmission method, although the CG timer is not started during the period when the terminal device sends N PUSCHs, the terminal device still believes that the CG timer is running during this period. This can prevent the terminal device using the same HARQ process from sending a new PUSCH and overwriting the buffer in the process, thus preventing the subsequent PUSCH transmission from being completed.

[0235] The CG timer is started after the Nth CB-CG transmission opportunity to account for the possibility that the network device may not have correctly received the previous N-1 PUSCH transmissions. Only the PUSCH based on the Nth CB-CG transmission opportunity can determine whether to schedule a retransmission. Before possible retransmission scheduling, the terminal device cannot let the CG timer expire too early, which would cause the HARQ process buffer to be flushed.

[0236] Scenario 2: The impact on the CG timer in CRDSA-based CB-CG transmission mode.

[0237] In some embodiments, the CG timer is started after the last CB-CG transmission opportunity in the CB-CG resource group used for transmitting PUSCH. Between the first CB-CG transmission opportunity selected by the terminal device and the last CB-CG transmission opportunity, the terminal device considers the CG timer to be running.

[0238] Similar to the DSA-based CB-CG transmission method, after the introduction of the CRDSA-based CB-CG transmission method, although the CG timer is not started between the first and last CB-CG transmission time of the terminal device, the terminal device still considers the CG timer to be running during this period. This can prevent the terminal device using the same HARQ process from sending a new PUSCH that would overwrite the buffer in the process, thus preventing the subsequent PUSCH transmission or the retransmission scheduled by the network device from being completed.

[0239] The CG timer is started after the last CB-CG transmission in the CB-CG resource group used for PUSCH transmission. This is to take into account the base station using joint interference cancellation and the situation where all PUSCH transmissions except those in the CB-CG resource group used for PUSCH transmission are not received correctly. Only based on the last CB-CG transmission can a decision be made on whether to schedule a retransmission. Before possible retransmission scheduling, the terminal device cannot let the CG timer expire too early, which would cause the HARQ process buffer to be flushed.

[0240] Scenario 3: The impact on the CG retransmission timer in DSA-based CB-CG transmission mode.

[0241] In some embodiments, a CG retransmission timer is started after the Nth CB-CG transmission opportunity in the CB-CG resource group used for transmitting PUSCH.

[0242] The CG retransmission timer is used to manage and control the PUSCH retransmission process.

[0243] The Nth CB-CG transmission opportunity refers to the last CB-CG transmission opportunity selected by the terminal device. After completing the transmission of the last PUSCH, the terminal device starts the CG retransmission timer.

[0244] In some embodiments, if the terminal device receives a new transmission from the HARQ process used by the scheduling PUSCH during the operation of the CG retransmission timer, the CG retransmission timer is stopped.

[0245] In some embodiments, when the CG retransmission timer times out, the terminal device automatically retransmits the above N PUSCHs.

[0246] The CG retransmission timer is started after the Nth CB-CG transmission opportunity because the network device may not have correctly received the previous N-1 PUSCH transmissions. Only based on the Nth CB-CG transmission opportunity can a decision be made on whether to schedule a new transmission. Before a possible new transmission is scheduled, the terminal device cannot let the CG retransmission timer expire prematurely, thus causing automatic retransmission.

[0247] Scenario 4: Impact of CRDSA-based CB-CG transmission mode on the CG retransmission timer

[0248] In some embodiments, a CG retransmission timer is started after the last CB-CG transmission in the CB-CG resource group used to transmit PUSCH.

[0249] Unlike DSA-based CB-CG transmission, in CRDSA-based CB-CG transmission, the terminal device starts the CG retransmission timer after the last CB-CG transmission opportunity in the CB-CG resource group used for PUSCH transmission. This takes into account the base station using joint interference cancellation and the situation where all PUSCH transmissions except those in the CB-CG resource group used for PUSCH transmission have not been received correctly. The decision to schedule a new transmission can only be made based on the last CB-CG transmission opportunity. Before possible new transmission scheduling, the terminal device cannot let the CG timer expire prematurely, thus causing automatic retransmission.

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

[0251] Please refer to Figure 8, 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 a terminal device or can be installed within a terminal device. As shown in Figure 8, the device 800 may include a transmitting module 810 and a processing module 820.

[0252] The sending module 810 is used to send N PUSCHs during CB-CG transmission, where N is an integer greater than 1.

[0253] Processing module 820 is used to start at least one first timer based on the N PUSCH.

[0254] In some embodiments, the processing module 820 is configured to start a first timer when each PUSCH transmission is completed.

[0255] In some embodiments, the processing module 820 is further configured to start a second timer after the first timer expires for each first timer.

[0256] In some embodiments, during the operation of the target second timer, when the terminal device receives a new transmission or retransmission of the HARQ process used by the network device to schedule the PUSCH, or when the network device indicates that the PUSCH has been successfully received, the processing module 820 is further configured to: stop the target second timer; stop the first timer that has been started or is yet to be started; stop the second timer that has been started or is yet to be started; stop the PUSCH at the selected but not yet transmitted CB-CG transmission time in the CB-CG resource group used to send the PUSCH; wherein, the target second timer is any one of the second timers.

[0257] In some embodiments, the processing module 820 is configured to start a first timer when the earliest of the N PUSCHs is sent.

[0258] In some embodiments, the processing module 820 is further configured to start a second timer after the first timer expires.

[0259] In some embodiments, the duration of the second timer is related to at least one of the following: the timing of the CB-CG transmission used by the earliest PUSCH, the CB-CG resource group used to transmit the PUSCH, and the timing of the last CB-CG transmission in the CB-CG resource group used to transmit the PUSCH.

[0260] In some embodiments, the duration of the second timer is determined based on the configured duration of the second timer and a first duration, the first duration being related to at least one of the following: the CB-CG transmission timing of the earliest PUSCH, the CB-CG resource group used to transmit the PUSCH, and the last CB-CG transmission timing in the CB-CG resource group used to transmit the PUSCH.

[0261] In some embodiments, the N PUSCHs use the same HARQ process.

[0262] In some embodiments, when the CB-CG transmission process is a DSA-based CB-CG transmission process, the contents contained in the N PUSCHs may be the same or different; or, when the CB-CG transmission process is a CRDSA-based CB-CG transmission process, the contents contained in the N PUSCHs may be the same.

[0263] In some embodiments, the PUSCH carries first information, which is used to indicate the transmission timing of each of the N PUSCHs.

[0264] In some embodiments, the number of PUSCHs is configured by the network device or determined by the terminal device based on the maximum number configured by the network device.

[0265] In some embodiments, the processing module 820 is configured to select a target CB-CG resource group from a plurality of CB-CG resource groups, each CB-CG resource group containing a plurality of CB-CG transmission opportunities; and randomly select N CB-CG transmission opportunities from the plurality of CB-CG transmission opportunities contained in the target CB-CG resource group for sending the PUSCH.

[0266] In some embodiments, the CB-CG resource group is determined based on at least one of the following: time window, time domain start position, maximum number of transmission opportunities, period, and offset value.

[0267] In some embodiments, the apparatus 800 further includes a receiving module (not shown in FIG8) for receiving configuration information for indicating whether to use joint interference cancellation technology to receive the PUSCH.

[0268] In some embodiments, when the configuration information indicates that the joint interference cancellation technique is not used to receive the PUSCH, the terminal device starts a timer when each PUSCH transmission is completed; when the configuration information indicates that the joint interference cancellation technique is used to receive the PUSCH, the terminal device starts a first timer when the earliest of the N PUSCHs is transmitted.

[0269] In some embodiments, a CG timer is started after the Nth CB-CG transmission opportunity in the CB-CG resource group used for transmitting the PUSCH, and the terminal device considers the CG timer to be running between the first CB-CG transmission opportunity selected by the terminal device and the Nth CB-CG transmission opportunity; or, a CG timer is started after the last CB-CG transmission opportunity in the CB-CG resource group used for transmitting the PUSCH, and the terminal device considers the CG timer to be running between the first CB-CG transmission opportunity selected by the terminal device and the last CB-CG transmission opportunity.

[0270] In some embodiments, a CG retransmission timer is started after the Nth CB-CG transmission opportunity in the CB-CG resource group used to transmit the PUSCH; or, a CG retransmission timer is started after the last CB-CG transmission opportunity in the CB-CG resource group used to transmit the PUSCH.

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

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

[0273] Please refer to Figure 9, which shows a schematic diagram of the structure of a terminal device 900 provided in one embodiment of this application. The terminal device 900 can be used to execute the method steps performed by the terminal device in the above embodiments. The terminal device 900 may include: a processor 901, a transceiver 902, and a memory 903. The transceiver 902 is used to implement the functions of the above-mentioned transmitting module and / or receiving module, and the processor 901 can be used to implement other processing functions or control transmitting and / or receiving.

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

[0275] The transceiver 902 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.

[0276] The memory 903 can be connected to the processor 901 and the transceiver 902.

[0277] The memory 903 can be used to store a computer program executed by the processor, and the processor 901 is used to execute the computer program to implement the various steps executed by the terminal device in the above method embodiments.

[0278] Furthermore, the memory 903 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, static on-demand memory, read-only memory, magnetic memory, flash memory, and programmable read-only memory.

[0279] In some embodiments, the transceiver 902 is configured to send N PUSCHs during CB-CG transmission, where N is an integer greater than 1. The processor 901 is configured to start at least one first timer based on the N PUSCHs.

[0280] For details not described in the above embodiments, please refer to the descriptions in the above method embodiments, which will not be repeated here.

[0281] This application also provides a computer-readable storage medium storing a computer program that is executed by a processor to implement the above-described wireless communication method.

[0282] 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).

[0283] This application also provides a chip, which includes programmable logic circuits and / or program instructions, and is used to implement the above-described wireless communication method when the chip is running.

[0284] This application also provides a computer program product, which includes a computer program stored in a computer-readable storage medium. A processor reads and executes the computer program from the computer-readable storage medium to implement the above-described wireless communication method.

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

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

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

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

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

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

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

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

[0293] 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 method of wireless communication, the method comprising: The method is performed by a terminal device, and the method comprises: In a contention-based configured grant (CB-CG) transmission process, N physical uplink shared channels (PUSCHs) are transmitted, N being an integer greater than 1; At least one first timer is started based on the N PUSCHs.

2. The method of claim 1, wherein, The starting of the at least one first timer based on the N PUSCHs comprises: When each PUSCH transmission is completed, a first timer is started.

3. The method of claim 2, wherein, The method further comprises: For each first timer, after the first timer expires, a second timer is started.

4. The method of claim 3, wherein, During running of a target second timer, in a case where the terminal device receives a new transmission or retransmission of a hybrid automatic repeat request (HARQ) process used by the network device to schedule the PUSCH or the network device indicates that the reception of the PUSCH is successful, the method further comprises at least one of the following: Stopping the target second timer; Stopping a first timer that has been started or is to be started; Stopping a second timer that has been started or is to be started; Stopping a PUSCH on a selected but not yet transmitted CB-CG transmission occasion in a CB-CG resource group used for transmitting the PUSCH; The target second timer is any one of the second timers.

5. The method of claim 1, wherein, The starting of the at least one first timer based on the N PUSCHs comprises: When the earliest one of the N PUSCHs is completed, a first timer is started.

6. The method of claim 5, wherein, The method further comprises: After the first timer expires, a second timer is started.

7. The method of claim 6, wherein, A duration of the second timer is related to at least one of the following: a CB-CG transmission occasion used by the earliest one of the PUSCHs, a CB-CG resource group used for transmitting the PUSCHs, and a last CB-CG transmission occasion in the CB-CG resource group used for transmitting the PUSCHs.

8. The method according to claim 6 or 7, characterized in that, The duration of the second timer is determined according to a configured duration of the second timer and a first duration, the first duration being related to at least one of the following: a CB-CG transmission occasion used by the earliest one of the PUSCHs, a CB-CG resource group used for transmitting the PUSCHs, and a last CB-CG transmission occasion in the CB-CG resource group used for transmitting the PUSCHs.

9. The method according to any one of claims 1 to 8, characterized in that, The N PUSCHs use a same HARQ process.

10. The method of any one of claims 1 to 9, wherein, In a case where the CB-CG transmission process is a DSA-based CB-CG transmission process, the N PUSCHs contain same or different contents; Or, In a case where the CB-CG transmission process is a CRDSA-based CB-CG transmission process, the N PUSCHs contain same contents.

11. The method according to any one of claims 1 to 10, characterized in that, The PUSCHs carry first information, the first information being used to indicate respective transmission occasions of the N PUSCHs.

12. The method according to any one of claims 1 to 11, characterized in that, The number of the PUSCHs is configured by a network device or determined by the terminal device based on a maximum number configured by the network device.

13. The method according to any one of claims 1 to 12, characterized in that, The method further comprises: selecting a target CB-CG resource group from a plurality of CB-CG resource groups, each CB-CG resource group containing a plurality of CB-CG transmission occasions; randomly selecting N CB-CG transmission occasions from the plurality of CB-CG transmission occasions contained in the target CB-CG resource group for transmitting the PUSCH.

14. The method of claim 13, wherein, The CB-CG resource group is determined according to at least one of the following information: a time window, a time domain starting position, a maximum number of transmission occasions, a period, and an offset value.

15. The method according to any one of claims 1 to 14, characterized in that, The method further includes: receiving configuration information, the configuration information being used to indicate whether to receive the PUSCH using a joint interference cancellation technology.

16. The method of claim 15, wherein, in a case where the configuration information indicates not to receive the PUSCH using the joint interference cancellation technology, the terminal device starts a timer upon completion of each PUSCH transmission; in a case where the configuration information indicates to receive the PUSCH using the joint interference cancellation technology, the terminal device starts a first timer upon completion of an earliest one of the N PUSCH transmissions.

17. The method of any one of claims 1 to 16, wherein, a CG timer is started after an Nth CB-CG transmission occasion in the CB-CG resource group used for transmitting the PUSCH, and the terminal device considers the CG timer to be running between a first CB-CG transmission occasion selected by the terminal device and the Nth CB-CG transmission occasion; or a CG timer is started after a last CB-CG transmission occasion in the CB-CG resource group used for transmitting the PUSCH, and the terminal device considers the CG timer to be running between a first CB-CG transmission occasion selected by the terminal device and the last CB-CG transmission occasion.

18. The method of any one of claims 1 to 17, wherein, a CG retransmission timer is started after an Nth CB-CG transmission occasion in the CB-CG resource group used for transmitting the PUSCH; or a CG retransmission timer is started after a last CB-CG transmission occasion in the CB-CG resource group used for transmitting the PUSCH. The apparatus includes: a sending module configured to send N physical uplink shared channels (PUSCHs) in a contention-based configured grant (CB-CG) transmission process, N being an integer greater than 1; 19. A wireless communication device, comprising: a processing module configured to start at least one first timer based on the N PUSCHs. The terminal device includes a processor and a memory, the memory storing a computer program, and the processor executes the computer program to implement the method of any one of claims 1 to 18. The storage medium stores a computer program, and the computer program is configured to be executed by a processor to implement the method of any one of claims 1 to 18.

20. A terminal device, comprising: ​ 21. A computer-readable storage medium, characterized in that, ​ 22. A chip, characterized by The chip comprises programmable logic circuitry and / or program instructions for implementing the method of any one of claims 1 to 18 when the chip is run.

23. A computer program product, characterised in that, The computer program product comprises computer instructions stored in a computer-readable storage medium, which are read and executed by a processor to implement the method of any one of claims 1 to 18.

Images