Wireless communication method and apparatus, device, and storage medium

Abstract

A wireless communication method and apparatus, a device, and a storage medium, relating to the technical field of communications. The method comprises: sending a plurality of first messages (step 610); for the plurality of first messages, starting at least one timer (step 620); and during operation of the timer, monitoring downlink information from a network device (step 630). In the method, on the one hand, a plurality of first messages are sent to a network device, thereby reducing the probability of transmission failure of a terminal device caused by conflicts of the first messages. On the other hand, the starting mode of a timer for the plurality of first messages can be flexibly set according to requirements. Moreover, during operation of the timer, downlink information from the network device is monitored, thereby determining a transmission result of the first messages.

Description

Wireless communication method, apparatus, device, and storage medium TECHNICAL FIELD

[0001] Embodiments of the present application relate to the technical field of communication, and particularly relate to a wireless communication method, apparatus, device and storage medium. BACKGROUND

[0002] In a contention-based communication scenario, how to reduce the transmission failure probability caused by transmission conflict needs further research.

[0003] SUMMARY

[0004] Embodiments of the present application provide a wireless communication method, apparatus, device and storage medium. The technical solutions provided by the present application are as follows:

[0005] According to an aspect of embodiments of the present application, a wireless communication method is provided, the method is executed by a terminal device, and the method comprises:

[0006] sending a plurality of first messages;

[0007] starting at least one timer for the plurality of first messages;

[0008] monitoring downlink information from a network device during running of the timer.

[0009] According to an aspect of embodiments of the present application, a wireless communication apparatus is provided, the apparatus comprises:

[0010] a sending module configured to send a plurality of first messages;

[0011] a processing module configured to start at least one timer for the plurality of first messages;

[0012] The processing module is further configured to monitor downlink information from a network device during running of the timer.

[0013] According to an aspect of embodiments of the present application, a terminal device is provided, the terminal device comprises a processor and a memory, the memory stores a computer program, and the processor executes the computer program to implement the above wireless communication method.

[0014] According to an aspect of embodiments of the present application, a computer readable storage medium is provided, the storage medium stores a computer program, and the computer program is configured to be executed by a processor to implement the above wireless communication method.

[0015] According to an aspect of embodiments of the present application, a chip is provided, the chip comprises a programmable logic circuit and / or program instructions, and when the chip is running, the programmable logic circuit and / or program instructions are configured to implement the above wireless communication method.

[0016] According to an aspect of the embodiments of the present application, a computer program product is provided, which includes computer instructions stored in a computer readable storage medium, and a processor reads and executes the computer instructions from the computer readable storage medium to implement the above wireless communication method.

[0017] The technical scheme provided by the embodiments of the present application can include the following beneficial effects:

[0018] On the one hand, by sending multiple first messages to the network device, the probability of transmission failure of the terminal device due to the collision of the first messages can be reduced. On the other hand, the starting mode of the timer of the multiple first messages can be flexibly set according to the needs. And during the running period of the timer, the transmission result of the first message can be determined by monitoring the downlink information from the network device. BRIEF DESCRIPTION OF DRAWINGS

[0019] FIG. 1 is a schematic diagram of a network architecture provided by an embodiment of the present application;

[0020] FIG. 2 is a schematic diagram of a contention-based random access method provided by an embodiment of the present application;

[0021] FIG. 3 is a schematic diagram of a non-contention-based random access method provided by an embodiment of the present application;

[0022] FIG. 4 is a flowchart of EDT under a user plane transmission scheme provided by an embodiment of the present application;

[0023] FIG. 5 is a schematic diagram of data packet sending in a TDMA RA frame provided by an embodiment of the present application;

[0024] FIG. 6 is a flowchart of a wireless communication method provided by an embodiment of the present application;

[0025] FIG. 7 is a schematic diagram of multiple first message sending methods provided by an embodiment of the present application;

[0026] FIG. 8 is a block diagram of a wireless communication device provided by an embodiment of the present application;

[0027] FIG. 9 is a structural schematic diagram of a terminal device provided by an embodiment of the present application. DETAILED DESCRIPTION

[0028] In order to make the purpose, technical scheme and advantages of the present application clearer, the embodiments of the present application will be further described in detail below with reference to the drawings.

[0029] The network architecture and service scenarios described in the embodiments of the present application are used to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided by the embodiments of the present application. Those skilled in the art can know that, with the evolution of network architecture and the appearance of new service scenarios, the technical solutions provided by the embodiments of the present application are also applicable to similar technical problems.

[0030] The technical solutions of the embodiments of the present application can be applied to various communication systems, such as: Global System of 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, evolved system of NR system, LTE-based access to unlicensed spectrum (LTE-U) system, NR-based access to unlicensed spectrum (NR-U) system, Non-Terrestrial Networks (NTN) system, Universal Mobile Telecommunication System (UMTS), Wireless Local Area Networks (WLAN), Wireless Fidelity (WiFi), 5th-Generation (5G) system, B5G (Beyound 5G) system, 6th-Generation (6G) system or other communication systems, etc.

[0031] Generally, a conventional communication system supports a limited number of connections and is easy to implement. However, with the development of communication technology, a mobile communication system will not only support conventional communication, but also support, 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, and the like. Embodiments of the present application can also be applied to these communication systems.

[0032] The communication system in the embodiments of the present application can be applied to a Carrier Aggregation (CA) scenario, a Dual Connectivity (DC) scenario, or a Standalone (SA) network deployment scenario.

[0033] The communication system in the embodiments of the present application can be applied to an unlicensed spectrum, which can also be considered as a shared spectrum. Alternatively, the communication system in the embodiments of the present application can also be applied to a licensed spectrum, which can also be considered as a non-shared spectrum.

[0034] The embodiments of the present application can be applied to a Non-Terrestrial Networks (NTN) system or a Terrestrial Networks (TN) system. The NTN generally adopts a satellite communication mode to provide communication services to users on the ground. The NTN system currently includes an NR-NTN and an IoT-NTN system, and other NTN systems can be included in the future.

[0035] Referring to FIG. 1, a schematic diagram of a network architecture 100 is shown according to an embodiment of the present application. The network architecture 100 can include a terminal device 10, an access network device 20, and a core network element 30.

[0036] The terminal device 10 can refer to a UE (User Equipment), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile, a remote station, a remote terminal, a mobile device, a wireless communication device, a user agent, or a user equipment. In some embodiments, the terminal device 10 can also be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol) phone, a WLL (Wireless Local Loop) station, a PDA (Personal Digital Assistant), a handheld device with wireless communication function, a computing device, or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, a terminal device in a 5GS (5th Generation System), or a terminal device in a future evolved PLMN (Public Land Mobile Network), etc., and the embodiments of the present application are not limited thereto. For the convenience of description, the above-mentioned devices 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 in a cell managed by each access network device 20. The terminal device can also be simply referred to as a terminal or a UE, and those skilled in the art can understand its meaning.

[0037] The access network device 20 is a device deployed in an access network to provide wireless communication functions for the terminal device 10. The access network device 20 can include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems using different wireless access technologies, the names of devices with access network device functions can be different, for example, in a 5G NR system, it is called gNodeB or gNB. As communication technology evolves, the name of the "access network device" may change. For ease of description, in the embodiments of the present application, the above-mentioned devices that provide wireless communication functions for the terminal device 10 are collectively referred to as access network devices. In some embodiments, through the access network device 20, a communication relationship can be established between the terminal device 10 and the core network element 30. Illustratively, in the LTE (Long Term Evolution) system, the access network device 20 can be an EUTRAN (Evolved Universal Terrestrial Radio Access Network) or one or more eNodeBs in the EUTRAN; in the 5G NR system, the access network device 20 can be a RAN (Radio Access Network) or one or more gNBs in the RAN. In the embodiments of the present application, the "network device" refers to the access network device 20, such as a base station, unless otherwise specified.

[0038] The core network element 30 is a network element deployed in the core network, and the main functions of the core network element 30 are to provide user connection, management of users, and completion of bearer for services, and to provide an interface to external networks as a bearer network. For example, the core network element in the 5G NR system can include an AMF (Access and Mobility Management Function) entity, a UPF (User Plane Function) entity, and an SMF (Session Management Function) entity, and the like.

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

[0040] The "5G NR system" in the embodiments of the present application can also be referred to as a 5G system or an NR system, but those skilled in the art can understand its meaning. The technical solutions described in the embodiments of the present application can be applicable to the LTE system, and can also be applicable to the 5G NR system, and can also be applicable to the subsequent evolution system (for example, the B5G (Beyond 5G, Super Five Generation Mobile Communication Technology) system, the 6G system (6th Generation System, the sixth generation mobile communication system)) of the 5G NR system, and can also be applicable to other communication systems such as the NB-IoT (Narrow Band Internet of Things, Narrow Band Internet of Things) system, and the present application does not limit this.

[0041] In the embodiments of the present application, the network device can provide services for a cell, and the terminal device communicates with the network device through the transmission resource (for example, the frequency domain resource, or the spectrum resource) on the carrier used by the cell. The cell can be a cell corresponding to the network device (for example, a base station), and the cell can belong to a macro base station or a base station corresponding to a small cell (Small cell). The small cell can include a metro cell, a micro cell, a pico cell, a femto cell, and the like. These small cells have the characteristics of small coverage and low transmit power, and are suitable for providing high-rate data transmission services.

[0042] Before introducing the technical solutions of the present application, some related technical knowledge involved in the present application will be introduced and described. The following related technologies can be combined with the technical solutions of the embodiments of the present application in any way, and all belong to the protection scope of the embodiments of the present application. The embodiments of the present application include at least part of the following contents.

[0043] 1. LTE random access procedure

[0044] In LTE, the random access procedure is mainly triggered by the following events:

[0045] 1. Establishing a wireless connection when the UE initially accesses: the UE transits from the RRC (Radio Resource Control) IDLE state (idle state) to the RRC CONNECTED state (connected state);

[0046] 2. RRC connection reestablishment procedure: in order to reestablish a wireless connection after a radio link failure;

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

[0048] 4. In RRC_CONNECTED state, DL (DownLink) data arrives, at this time, UL is in out-of-synchronization state;

[0049] 5. In RRC_CONNECTED state, UL (UpLink) data arrives, at this time, UL is in out-of-synchronization state or there is no PUCCH resource for sending SR;

[0050] 6. SR failure;

[0051] 7. Synchronization reconfiguration request from RRC.

[0052] In LTE, the following two random access methods are mainly supported, i.e., contention-based random access method and non-contention-based random access method, and the application scenarios of the above two methods are different. In the contention-based random access method, for terminal devices, RACH (Random Access Channel) is a resource pool that can be selected, and different terminal devices can use the same resource, resulting in resource competition. In the non-contention-based random access method, specific resources are reserved and allocated to a specific terminal device at a certain time.

[0053] FIG. 2 shows the contention-based random access method, the main features of which are code resource sharing and "four-step" access method, including access request, access response, connection request, and contention resolution (also known as conflict resolution). The process includes the following steps Step1-Step4. It should be noted that the interaction messages of each step in the contention-based random access method are respectively called Msg1-Msg4.

[0054] Step1: Access request (Msg1)

[0055] The terminal device selects PRACH (Physical Random Access Channel) resources (including time-frequency resources and code domain resources) and sends the selected preamble on the selected PRACH time-frequency resources. The network device can estimate the uplink timing (Timing) and the grant size required for the terminal device to transmit Msg3 based on the preamble.

[0056] Step2: Access response (Msg2)

[0057] After the network device receives the preamble sent by the terminal device, the network device sends a RAR (Random Access Response, random access response) to the terminal device. After the terminal device sends Msg1, a RAR window (window) is opened, and the terminal device monitors the PDCCH (Physical Downlink Control Channel, physical downlink control channel) scrambled by the RA-RNTI (Random Access-Radio Network Temporary Indentifier, random access-radio network temporary identifier) in the window.

[0058] In the LTE system, the calculation of the RA-RNTI is as follows:

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

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

[0061] In the NR system, the calculation of the RA-RNTI is as follows:

[0062] RA-RNTI = 1 + s_id + 14*t_id + 14*80*f_id + 14*80*8*ul_carrier_id

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

[0064] For eMTC (enhanced Machine-Type Communication, enhanced machine type communication) UEs, the calculation of the RA-RNTI is as follows:

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

[0066] where t_id is the index of the first subframe of PRACH transmission (0≤t_id<10), f_id is the frequency domain index corresponding to PRACH in the subframe (0≤f_id<6), where PRACH resources are numbered in ascending order in the frequency domain. SFN_id is the index of the first SFN (System Frame) of PRACH transmission, and Wmax is the maximum RAR window length that eMTC can support, which is 400 subframes.

[0067] For NB-IoT UEs, the calculation of RA-RNTI is as follows:

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

[0069] where SFN_id is the index of the first SFN of PRACH transmission, and carrier_id is the index of the UL carrier corresponding to PRACH transmission. The carrier_id of the anchor carrier is 0.

[0070] For NB-IoT UEs in TDD (Time Division Duplexing) mode, the calculation of RA-RNTI is as follows:

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

[0072] where SFN_id is the index of the first SFN of PRACH transmission, and H-SFN is the index of the first H-SFN (Hyper Frame) of PRACH transmission.

[0073] From the above calculation formula of RA-RNTI, it can be seen that RA-RNTI is related to the PRACH time-frequency resource used by the terminal device to send Msg1.

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

[0075] The subheader of RAR contains BI (Backoff Indicator), which is used to indicate the backoff time for retransmitting Msg1.

[0076] RAPID (Random Access Preamble ID) in RAR: the network responds to the preamble index received;

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

[0078] UL grant in RAR: used to schedule the uplink resource of Msg3; since the terminal device has not established an RRC connection with the network device and has not performed uplink synchronization, it cannot request an uplink grant from the network device through a scheduling request to perform uplink transmission, but can only carry uplink grant information in the RAR message to make the terminal device send the first uplink message Msg3, that is, RRCSetupRequest (RRC connection establishment request). The UL-Grant field indicates the resource used for uplink transmission. The length of the UL-Grant field is 20 bits, and Msg3 is actually sent using this resource.

[0079] Temporary C-RNTI in RAR, that is, TC-RNTI (Temporary Cell-RNTI), is used to scramble the PDCCH of Msg4.

[0080] If the terminal device receives a PDCCH scrambled by RAR-RNTI and the RAR contains the preamble index it sent, the terminal considers that it has successfully received the random access response.

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

[0082] Step 3: Connection request (Msg3)

[0083] Msg3 is mainly used to inform the network device that the RACH process is triggered by what event. For example, if it is an initial access random process, it will carry the UE ID and establishment cause in Msg3; if it is an RRC reestablishment, it will carry the connected UE identifier and establishment cause. At the same time, the ID carried by Msg3 can make the contention conflict be solved in Step 4.

[0084] Step 4: Contention resolution (Msg4)

[0085] Msg4 has two functions, the first is used for contention resolution, and the second is to transmit an RRC configuration message to the terminal device.

[0086] There are two ways to resolve contention: Way one, if the terminal device carries C-RNTI in Msg3, Msg4 is scheduled by PDCCH scrambled with C-RNTI. Way two, if the terminal device does not carry C-RNTI in Msg3, such as initial access, Msg4 is scheduled by PDCCH scrambled with TC-RNTI. The resolution of the conflict is achieved by the terminal device receiving the PDSCH carrying Msg4, and matching whether the CCCH (Common Control Channel) SDU (Service Data Unit) in the PDSCH and the contention resolution ID in its own Msg3 are the same.

[0087] Figure 3 shows a non-contention-based random access method, which is mainly characterized by code resource monopoly and a "three-step" access method, including preamble allocation, access request, and access response. The process includes the following steps Step0-Step2. It should be noted that we call the interaction message of each step in the non-contention-based random access method Msg0- Msg2, respectively.

[0088] Step0: Preamble allocation (Msg0)

[0089] The network device allocates a random access preamble to the terminal device and sends it using an RRC message or DCI (Downlink Control Information).

[0090] Step1: Access request (Msg1)

[0091] Step2: Access response (Msg2)

[0092] The description of Msg1 and Msg2 can be referred to the above, which will not be repeated here.

[0093] As can be seen from the above random access process, the main purpose of random access is for the terminal device to synchronize with the cell. In the random access process, the network device can know the time when the terminal device sends the preamble according to the RACH time-frequency resources used by the preamble received from the terminal device, so as to determine the initial TA (Timing Advance) of the terminal device according to the sending time and receiving time of the preamble, and inform the terminal through the RAR.

[0094] 2. EDT (Early Data Transmission, early data transmission)

[0095] In the conventional LTE system, if the terminal device in the RRC IDLE state has uplink data to be transmitted, the terminal device needs to initiate the RRC connection establishment through the random access process first, and can transmit data to the network device only after the RRC connection is established with the network device. In order to reduce the signaling interaction between the terminal device and the network device caused by data transmission and save the terminal power consumption, the EDT mechanism is introduced for NB-IoT and eMTC. This feature enables the terminal device in the RRC IDLE state to transmit UL data through Msg3 in the random access process. After receiving the successful reception response from the network device, the random access process is terminated, and the terminal device continues to remain in the RRC IDLE state without entering the RRC connected state. The network device configures a separate PRACH resource for EDT, and when the amount of UL data to be transmitted by the terminal device does not exceed the upper limit of the data amount configured by the network device, the terminal device can send Msg1 on the EDT separate PRACH resource, thereby requesting the Msg3 grant for EDT from the network device. As shown in 400 of FIG. 4, it is a flowchart of EDT under the user plane transmission scheme, and MME in FIG. 4 refers to Mobility Management Entity (Mobility Management Entity), and S-GW refers to Serving Gateway (Serving Gateway).

[0096] 3. PUR (Preconfigured Uplink Resources, preconfigured uplink resources)

[0097] In order to further reduce the signaling overhead and terminal power consumption on the basis of EDT, the PUR feature is introduced for NB-IoT and eMTC. This feature allows the base station to configure PUR resources for the UE when releasing the UE to the RRC IDLE state, so that the UE can use the PUR resources for uplink transmission in the RRC IDLE state without initiating the random access process. The network can also configure a DMRS (cyclic shift) at the same time when configuring the PUR for the UE, so that at most 2 UEs can share the same PUSCH (Physical Uplink Shared Channel) resource (at this time, different UEs are distinguished by DMRS). By skipping the random access process, the uplink transmission efficiency can be further improved and the terminal energy consumption can be further reduced.

[0098] Before performing the PUR transmission, the UE needs to verify the TA validity, and the TA validity is judged based on one or more of the following conditions:

[0099] a) Whether the serving cell is changed;

[0100] b) whether TAT is expired;

[0101] c) UE RSRP (Reference Signal Receiving Power) change.

[0102] To reduce the uplink and downlink signaling overhead and improve the system uplink capacity, further enhancements to EDT feature are planned in R19 IoT NTN, for example, introducing RACH-less EDT, i.e. direct transmission of Msg3, i.e. transmitting Msg3 directly without going through Msg1 / Msg2 procedure. The research goals of this feature are as follows: Study and specify, if beneficial the following enhancements to reduce the necessary uplink and downlink signaling to complete an EDT transaction [RAN2]: Msg3 transmission without msg1 / RAR; Efficient delivery (reduced overhead) of msg4 / RRC EarlyDataComplete.

[0103] In legacy EDT, the base station allocates PUSCH resource for Msg3 initial transmission to UE through Msg2, while in legacy PUR, the base station provides PUR configuration information to UE through RRC connection release message when releasing the UE to RRC IDLE state. For the PUSCH resource used for Msg3 transmission in RACH-less EDT, RAN2#126 has reached the following conclusion: RAN2 focusses the study on contention-based Msg3 transmission to complete an EDT-like transaction (FFS on the details of Msg3. FFS on the procedural steps, e.g. how much we reuse of EDT and PUR procedures. FFS on allocation of resources) (RAN 2 focuses on the study of contention-based Msg3 transmission to complete an EDT-like transaction (FFS on the details of Msg3. FFS on the procedural steps, e.g. how much we reuse of EDT and PUR procedures. FFS on allocation of resources)).

[0104] Based on the above conclusion, in RACH-less EDT, if multiple UEs select the same PUSCH resource to transmit Msg3 (i.e. multiple UEs have Msg3 collision), at this time the base station can successfully receive the Msg3 of at most one UE, and in most cases the Msg3 of all these colliding UEs cannot be correctly received by the base station. In this way, for the UE whose contention resolution fails, it needs to reattempt Msg3 transmission. Similarly, for CBRA (Contention-Based Random Access), for the UEs that select the same RO (RACH Occasion) and the same preamble to send Msg1, only after Msg4 reception can it be known whether the contention resolution is successful. For the UE whose contention resolution fails, it needs to reattempt Msg1. Msg3 collision in RACH-less EDT and Msg1 collision in CBRA on the one hand wastes system PUSCH and PRACH resources, and on the other hand the latency of UE sending data or access is also increased, thereby affecting the user experience.

[0105] In some satellite communication standards nowadays, DSA (Diversity Slotted Aloha) or CRDSA (Contention Resolution Diversity Slotted Aloha) is adopted to effectively improve the utilization of random access resources while reducing the probability of collision among different UEs. Taking RACH-less EDT as an example, the basic idea of DSA is that a UE sends multiple copies of Msg3 using different Msg3 transmissions, and as long as the base station successfully receives one of the Msg3s, the UE can consider the EDT successful. As can be seen, DSA increases the probability of successful reception of Msg3 by the base station by increasing the transmission opportunities of Msg3, thereby improving the system capacity. CRDSA is a further enhancement technique based on DSA, in which a UE sends multiple copies of Msg3 using different Msg3 transmissions, and the base station stores all the received data within a complete frame and uses interference cancellation techniques to enable the base station to successfully receive Msg3s sent from more UEs. Please refer to FIG. 5, which shows a schematic diagram of packet transmission within a TDMA RA frame. Each rectangular block in the figure represents a packet transmission, and the blocks filled with the same line represent packets sent by the same UE, while the blocks filled with different lines represent packets sent by different UEs. The numbers on the rectangular blocks are used to indicate the UE that sent the packet. For example, for the rectangular block with the number 1, it represents that the packet is sent by UE1. In FIG. 4, each packet has two copies, that is, each UE sends two copies of Msg3 using different Msg3 transmissions. FIG. 4 includes six UEs (UE1, UE2, UE3, UE4, UE5, and UE6), and each UE sends two packets. The base station can demodulate the packets sent by the six UEs in turn: UE3 -> UE2 (by canceling the packet of UE3) -> UE1 (by canceling the packet of UE2) -> UE6 (by canceling the packet of UE1). Finally, only the packets of UE4 and UE5 cannot solve the mutual conflict.

[0106] DSA and CRDSA technology is introduced in RACH-less EDT, hoping to reduce the probability of Msg3 collision of RACH-less EDT through DSA and CRDSA technology, so as to further improve the UL capacity. This technology can also be used in the RA process. After introducing DSA and CRDSA in RACH-less EDT and RA, what impact on the behavior of UE needs to be studied and specified from the standard level. That is, the application mainly studies the behavior of UE in the RACH-less EDT and RA process using DSA and CRDSA technology.

[0107] Please refer to FIG. 6, which shows a flowchart of a wireless communication method provided by an embodiment of the application. The method can be applied in the network architecture shown in FIG. 1. The method is executed by a terminal device, and the method can include at least one of the following steps (610-630).

[0108] Step 610, sending a plurality of first messages.

[0109] In some embodiments, the first message is a message sent by the terminal device to the network device for establishing a communication connection or requesting an uplink resource, so as to ensure that the terminal device can interact and transmit data with the network device.

[0110] The terminal device sends a plurality of first messages to the network device, which can reduce the probability of transmission failure of the terminal device due to first message collision compared to sending one first message, that is, improve the transmission success rate and reliability of the first message. In some embodiments, when solving the competition conflict based on the CRDSA method, the plurality of first messages contain the same content. Wherein, the content contained in the first message refers to the request or instruction sent by the terminal device to the network device, which can include device identification, data content, operation type, etc., and the application does not limit the content contained in the first message. In some embodiments, when solving the competition conflict based on DSA, the content contained in the plurality of first messages can be the same or different.

[0111] In some embodiments, the number of first messages sent is configured by the network device. Exemplarily, the number of first messages sent can be N, and the value of N can be indicated by the network device, N being an integer greater than or equal to 2. In some embodiments, the number of first messages sent is determined by the terminal device based on the maximum number configured by the network device. Exemplarily, assuming that the maximum number configured by the network device is N max , the number of first messages sent can be determined by the terminal device as N, wherein N is an integer greater than or equal to 2 and less than or equal to N max , and N max is an integer greater than or equal to 2. Through this method, the number of first messages sent can be flexibly determined.

[0112] Step 620, starting at least one timer for the plurality of first messages.

[0113] The timer is used to manage the timeout processing and status update of the response to the first message. Starting at least one timer for the plurality of first messages means that one timer can correspond to one first message, or at least two first messages. One timer corresponds to one first message, that is, one timer is used to manage one first message. Since the processing logic and timeout mechanism of each timer can be independently set, the timeout processing and status update of the response to each first message can be managed individually, achieving precise control of each first message. When one timer corresponds to at least two first messages, that is, a single timer uniformly manages at least two first messages. In this way, when the number of first messages sent is large, timer resources can be saved and management can be simplified.

[0114] Step 630, monitoring the downlink information from the network device during the running of the timer.

[0115] In some embodiments, the running period of the timer is the period between the start of the specified timer and its timeout or being closed. During this period, the downlink information from the network device is monitored. In some embodiments, the downlink information refers to the downlink control information, which is used to feed back the reception status of the first message. The terminal device determines the transmission status of the first message according to the downlink information of the network device, that is, determines whether the first message is successfully received by the network device. In some embodiments, the downlink information is a first downlink channel scrambled by a first sequence. That is, the first downlink channel scrambled by the first sequence is monitored during the running of the timer. Wherein, the sequence can be RNTI, and the downlink channel can be PDCCH.

[0116] In some embodiments, the first sequence is associated with the terminal device, that is, the network device allocates a first sequence to each terminal device, that is, the timer monitors a plurality of first downlink channels scrambled by a plurality of first sequences, and the values of the plurality of first sequences are the same. In some embodiments, the first sequence is associated with the transmission resource of the first message, and the transmission resource can be time-frequency resource or time-frequency code resource. In some embodiments, the first sequence is determined based on the transmission resource of the first message. Since the transmission resources of the plurality of first messages are different, when the timer monitors a plurality of first downlink channels scrambled by a plurality of first sequences, the values of the plurality of first sequences are different.

[0117] In summary, the technical scheme provided by the embodiments of the present application can reduce the probability of transmission failure of the terminal device caused by the collision of the first messages by sending multiple first messages to the network device. On the other hand, the starting mode of the timer of the multiple first messages can be flexibly set according to the requirement. During the running period of the timer, the transmission result of the first message can be determined by monitoring the downlink information from the network device, and the transmission result refers to whether the first message is successfully received by the network device.

[0118] In some embodiments, the sending mode of the multiple first messages can be any one of the following three modes: TDM (Time Division Multiplexing), FDM (Frequency Division Multiplexing), and joint TDM and FDM. The specific implementation of starting the timer will be introduced based on the above three sending modes. The step 620 can be implemented as any one of the following steps 621, 622 and 623 (not shown in the figure).

[0119] Step 621: For the multiple first messages, multiple timers are started, and each timer corresponds to a first message. Wherein the multiple first messages are sent in TDM mode.

[0120] The multiple messages are sent in TDM mode, which means that the multiple messages are transmitted in different time domain resources in the time domain. The time domain resource refers to the transmission resource that is divided and managed in time, which can be a time slot, a symbol, a frame, a subframe, etc., which is not limited in the present application. For example, the multiple messages are sent in different time slots, as shown in subgraph 1 of FIG. 7, the horizontal axis is time, and the vertical axis is frequency. The first message 71 can be sent in time slot a, and the first message 72 can be sent in time slot b. The first message 71 can correspond to timer 1, and the first message 72 can correspond to timer 2, wherein the timer 1 and the timer 2 are two different timers.

[0121] In some embodiments, the starting time of the timer can be determined as starting a timer at each time when a first message transmission is completed. In some embodiments, the starting time of the timer can be determined as starting a timer at each time when a first message transmission is completed. For example, as shown in subgraph 1 of FIG. 7, a timer can be started at the end of the first message 71, i.e., at the end of the time slot a. In some embodiments, the starting time of the timer can be determined as starting a timer at a first interval after each time when a first message transmission is completed, and the first interval is determined based on the round-trip time (RTT) between the terminal device and the network device. In some embodiments, the first interval can also be a preset time interval, which is not limited in the present application. For example, a timer can be started at the first interval after the end of the first message 71, i.e., at the end of the time slot a.

[0122] In step 622, a plurality of timers are started for the plurality of first messages, each timer corresponding to a first message; or a timer is started for the plurality of first messages. The plurality of first messages are transmitted in the FDM manner.

[0123] The plurality of messages are transmitted in the FDM manner, which means that the plurality of messages are transmitted in different frequency bandwidths in the frequency domain. The frequency bandwidth refers to a frequency range used for data transmission, which can be a subcarrier, a resource block (RB), etc., which is not limited in the present application. For example, as shown in subgraph 2 of FIG. 7, the horizontal axis represents time and the vertical axis represents frequency. The first message 73 can be transmitted in subcarrier a, and the first message 74 can be transmitted in subcarrier b. There are two ways to set the timer for the first message 73 and the first message 74. One way is that the first message 73 can correspond to timer 1, and the first message 74 can correspond to timer 2, wherein the timer 1 and the timer 2 are two different timers. Another way is that the first message 73 and the first message 74 correspond to the same timer.

[0124] In some embodiments, when each timer corresponds to one first message, the determination of the starting time of the timer can be that a timer is started at each time when a first message transmission is completed. In some embodiments, a timer is started at the end time of each completed first message transmission. For example, as shown in subgraph 2 of FIG. 7, a timer can be started at the end time of the completion of the first message 73, i.e., the end time of the time slot a. In some embodiments, the determination of the starting time of the timer can be that a timer is started at a first interval after each completed first message transmission, and the first interval is determined based on the round trip delay between the terminal device and the network device. In some embodiments, the first interval can also be a preset time interval, which is not limited in the present application. For example, a timer can also be started at the first interval after the end time of the completion of the first message 73, i.e., the end time of the time slot a.

[0125] In some embodiments, when one timer is started for multiple first messages, and the multiple first messages are completed at the same time, the determination of the starting time of the timer can be that a timer is started at the time when the multiple first messages are completed, or a timer is started at a first interval after the multiple first messages are completed. In some embodiments, the first interval can also be a preset time interval, which is not limited in the present application. For example, in the above example, assuming that the first message 73 and the first message 74 are completed at the same time, a timer can be started at the end time of the completion of the first message 73 or the first message 74, i.e., the end time of the time slot a. For example, a timer can also be started at a first interval after the end time of the completion of the first message 73 or the first message 74, i.e., a timer is started at a first interval after the end time of the time slot a.

[0126] In some embodiments, when a timer is started for the plurality of first messages, and the plurality of first messages are not transmitted at the same time, the starting time of the timer can be when a target first message of the plurality of first messages is transmitted, or when a first interval after the target first message of the plurality of first messages is transmitted, wherein the target first message is the first message of the plurality of first messages that is transmitted earliest, or the target first message is the first message of the plurality of first messages that is transmitted latest, and the first interval is determined based on the round-trip time between the terminal device and the network device. In some embodiments, the first interval can also be a preset time interval, which is not limited in the present application. In some embodiments, the first message of the plurality of first messages that is transmitted earliest refers to the first message of the plurality of first messages that is transmitted earliest in time, and the first message of the plurality of first messages that is transmitted latest refers to the first message of the plurality of first messages that is transmitted latest in time. For example, assuming that the first message 73 is transmitted earlier than the first message 74 in the above example, the first message 73 is the first message of the plurality of first messages that is transmitted earliest, and the first message 74 is the first message of the plurality of first messages that is transmitted latest. The target first message can be the first message 73 or the first message 74, which is not limited in the present application.

[0127] The above method can flexibly determine the transmission time of the timer based on different setting methods of the timer for the plurality of first messages. When each timer corresponds to a first message, each timer independently monitors and processes the transmission state of the corresponding first message. When a timer is started for the plurality of first messages, the timer monitors and processes the transmission state of the plurality of first messages.

[0128] In step 623, a plurality of timers are started for the plurality of first messages, each timer corresponding to a first message, or at least one timer is started according to the time when each of the plurality of first messages is transmitted. The plurality of first messages are transmitted in a joint TDM and FDM manner.

[0129] In some embodiments, the plurality of first messages are transmitted in a joint TDM and FDM manner, which means that the plurality of messages are transmitted using different time domain resources in the time domain and different frequency bandwidths in the frequency domain. For example, as shown in subgraph 3 of FIG. 7, the horizontal axis represents time and the vertical axis represents frequency. The first message 75 can be transmitted in time slot a and subcarrier a, the first message 76 can be transmitted in time slot a and subcarrier b, the first message 77 can be transmitted in time slot b and subcarrier a, and the first message 78 can be transmitted in time slot b and subcarrier b.

[0130] In some embodiments, for the first messages with different time instants of completing sending, one timer is started respectively; and for the first messages with the same time instant of completing sending, one timer is started.

[0131] It can be understood that for the first messages with the same time instant of completing sending, one timer can be started respectively for each first message. Since these first messages are completely consistent in time instant of completing sending, they can also be regarded as events triggered at the same time, and thus one timer can be started for all the first messages with the same time instant of completing sending. However, for the first messages with different time instants of completing sending, since the time instants of completing sending of these first messages are distributed at different time instants, the processing time of each first message can be different. Therefore, one timer can be started respectively for each first message, and one timer cannot be started for all the first messages with different time instants of completing sending. Exemplarily, as shown in subgraph 3 of FIG. 7, the time instants of completing sending of the first message 75 and the first message 76 are both t1, and the time instants of completing sending of the first message 77 and the first message 78 are both t2. Since the time instants of completing sending of the first message 75 and the first message 76 are the same, and the time instants of completing sending of the first message 77 and the first message 78 are the same, one timer can be started at the time instants of completing sending of the first message 75 and the first message 76, or one timer can be started for the first message 75 and another timer can be started for the first message 76; one timer can be started at the time instants of completing sending of the first message 77 and the first message 78, or one timer can be started for the first message 77 and another timer can be started for the first message 78. Exemplarily, since the time instants of completing sending of the first message 75 and the first message 77 are different, different timers are started respectively. Since the time instants of completing sending of the first message 76 and the first message 78 are different, different timers are started respectively.

[0132] In some embodiments, when the plurality of first messages are sent within the first time window, the step 620 can be implemented as the following step 624 (not shown in the figure).

[0133] The step 624 starts one timer for the plurality of first messages, wherein the plurality of first messages are sent within the first time window.

[0134] In some embodiments, the step 624 corresponds to the CRDSA technique introduced in the background section, the network device stores all the received first messages (e.g., Msg3) in a time window, and then demodulates all the received Msg3s in the time window by the interference cancellation technique. Therefore, for the terminal device, the terminal device needs to complete the transmission of multiple Msg3s in a time window. In some embodiments, the first time window is determined based on a starting time and a window length. The window length can be defined according to a preset or configured by the network, and the starting time can be determined according to the window length. For example, the window length can be 20 ms, and the starting time is the subframe id mode 20 = 0, i.e., the starting time is the position of subframes 0, 20, 40, 60, and so on.

[0135] In some embodiments, the starting time of the timer is determined based on the ending time of the first time window. In some embodiments, the starting time of the timer is determined based on the ending time of the first time window and a first interval length, and the first interval length is determined based on the round-trip time delay between the terminal device and the network device. In some embodiments, the first interval length can also be a preset time interval, which is not limited in the present application. In some embodiments, the ending time of the first time window can be determined according to the starting time and the window length. The ending time of the first time window can be the sum of the starting time and the window length.

[0136] For example, assuming that the ending time of the first time window is t, the terminal device can start a timer at time t1. Wherein, t1 = t + UE-eNB / gNB RTT + Tprocessing; or, t1 = t + Tprocessing. Wherein, UE-eNB / gNB RTT refers to the round-trip time delay between the terminal device and the network device, and the value of Tprocessing can be predefined or configured by the network device, and the value of Tprocessing is greater than or equal to 0.

[0137] To sum up, the present application is directed to different sending modes of multiple first messages, including four modes of using TDM, FDM, joint TDM and FDM for multiple first messages, and completing sending of multiple first messages in a first time window. For the four sending modes, the specific implementation mode of starting a timer is introduced, and the correspondence between the first message and the timer is introduced in detail, that is, one timer can correspond to one first message, or one timer can correspond to at least two first messages. The starting time of the timer is also introduced. On the one hand, the system can flexibly select the sending mode of multiple first messages. On the other hand, based on different sending modes, the starting mode of the corresponding timer can be determined, so that subsequent downlink information from the network device can be monitored to determine the transmission state of the first message.

[0138] The present application will introduce the specific implementation mode of determining the first message contention resolution situation for the following three application scenarios: contention-based small data transmission process, random access process, and contention-based uplink configured grant transmission process.

[0139] Scenario 1: Contention-based small data transmission process

[0140] In some embodiments, the first message is a message in a contention-based small data transmission procedure. In some embodiments, the small data transmission procedure can be the RACH-less EDT procedure described above, and the first message can be Msg3, and the timer can be a contention resolution timer (mac-ContentionResolutionTimer). In some embodiments, the contention resolution timer is used to determine a time period for waiting for contention resolution. In some embodiments, the terminal device receives configuration information of the RACH-less EDT from the network device, which can include Msg3 resource configuration information for the RACH-less EDT based on which multiple PUSCH transmission occasions for Msg3 transmission of the RACH-less EDT can be determined. In some embodiments, the terminal device can randomly select multiple PUSCH transmission occasions for sending multiple Msg3s using TDM, which correspond to different time domain resources. In some embodiments, the terminal device can randomly select multiple PUSCH transmission occasions for sending multiple Msg3s using FDM, which correspond to different frequency domain resources. In some embodiments, the terminal device can randomly select multiple PUSCH transmission occasions for sending multiple Msg3s using joint TDM and FDM, which correspond to different time-frequency resources. In some embodiments, the terminal device can randomly select multiple PUSCH transmission occasions for sending multiple Msg3s within a first time window, which can correspond to different time domain resources (based on TDM), different frequency domain resources (based on TDM), or different time-frequency resources (based on joint TDM and FDM).

[0141] In some embodiments, depending on the manner of starting the timer, the contention resolution of the first message is determined in the following three cases: starting multiple timers, each corresponding to a first message, starting one timer, and starting at least one timer.

[0142] Case 1 (1), starting multiple timers, each corresponding to a first message

[0143] In some embodiments, when multiple messages are sent in any one of TDM, FDM, and joint TDM and FDM, multiple timers can be started, and each timer corresponds to a first message.

[0144] In some embodiments, during running of a first timer in the plurality of timers, if the terminal device receives first information from the network device, the first timer is any one of the plurality of timers, the first timer is stopped; in a case where the first information satisfies a first condition, it is determined that the contention resolution is successful, and other timers being run are stopped. In some embodiments, when the terminal device encounters a collision in a contention environment (e.g., a plurality of terminal devices contend for uplink transmission resources), it is determined that the contention resolution is successful, that is, the network device responds to and determines the first message sent by the terminal device, so that the terminal device can complete subsequent uplink data transmission. Since the terminal device has determined that the contention resolution is successful, the system will stop other timers being run at this time to avoid unnecessary operations. In some embodiments, the first information is a MAC PDU. Before receiving the first information, the terminal device receives first downlink information scrambled by a first sequence (e.g., a PDCCH scrambled by an RNTI), which indicates PDSCH reception, and the terminal device acquires the first information by decoding a MAC PDU carried by the PDSCH. In some embodiments, the first condition includes that the first information contains a contention resolution MAC CE (Media Access Control Layer Control Element), and the contention resolution identifier indicated by the contention resolution MAC CE matches a CCCH (Common Control Channel) SDU (Service Data Unit) transmitted in the first message or matches part of bits in the CCCH SDU transmitted in the first message. That is, the Msg3 contains the contention resolution MAC CE, and the contention resolution identifier indicated by the contention resolution MAC CE matches the CCCH SDU transmitted in the Msg3 or matches part of bits in the CCCH SDU transmitted in the Msg3. The part of bits can be the first k bits, and k is a positive integer, which can be predefined.

[0145] In some embodiments, when the first timer times out, if all other timers have timed out or stopped, and the terminal device does not receive the first information satisfying the first condition, it is determined that the contention resolution fails. In some embodiments, the timer timeout means that the preset time limit of the timer is exceeded, which means that the first information satisfying the first condition is not received during the running of the timer. When all timers have timed out or stopped, it can be determined that each of the plurality of first messages fails to be successfully resolved, that is, the first message transmission fails.

[0146] In some embodiments, when the first timer expires, if the terminal device does not receive the third information from the network device before the expiration of the first timer, and all other timers have expired or stopped, and the terminal device does not receive the first information satisfying the first condition, it is determined that the contention resolution fails, wherein the third information is used to indicate retransmission of the first message. In some embodiments, when multiple first messages fail to be successfully transmitted or received, the network device sends the third information to the terminal device, which can include instructions related to retransmission operation, to inform the terminal device that the first message needs to be retransmitted, so as to re-establish the correct communication state when there is an error or loss in communication. In some embodiments, the third information is PDCCH. In some embodiments, when the terminal device does not receive the retransmission instruction for the first message from the network device before the expiration of the first timer, and all other timers have expired or stopped, and the terminal device does not receive the first information satisfying the first condition, it is determined that the contention resolution fails.

[0147] Case 1(2), start multiple timers, each timer corresponding to a first message

[0148] In some embodiments, when the first timer of the multiple timers expires, if the terminal device has received the second information before the expiration of the first timer, and the second information satisfies the second condition, it is determined that the contention resolution succeeds, and the other timers running are stopped, and the first timer is any one of the multiple timers. In some embodiments, the second information is PDCCH scrambled by the first RNTI. In some embodiments, the second condition includes: the second information indicates receiving PDSCH; the terminal device successfully decodes a medium access control layer protocol data unit (MAC PDU) carried by the PSDCH; the MAC PDU contains a contention resolution MAC CE, and the contention resolution MAC CE indicates that the contention resolution identifier matches the CCCH SDU transmitted in the first message, or matches part of the bits in the CCCH SDU transmitted in the first message. It can be understood that in this case, only the reception of the second information before the expiration of the first timer is limited, and the above steps of successfully decoding the MAC PDU carried by the PSDCH by the terminal device; the MAC PDU contains a contention resolution MAC CE, and the contention resolution MAC CE indicates that the contention resolution identifier matches the CCCH SDU transmitted in the first message, or matches part of the bits in the CCCH SDU transmitted in the first message are not limited to whether they are completed before the expiration of the first timer. That is, the above steps can be completed before the expiration of the first timer, corresponding to the above case 1(1), or the above steps can be completed after the expiration of the first timer, which is not limited by the present application.

[0149] In some embodiments, upon expiry of the first timer, if the terminal device does not receive the second information satisfying the second condition before the expiry of the first timer, and all other timers have expired or stopped, it is determined that the contention resolution fails. In some embodiments, upon expiry of the first timer, if the terminal device does not receive the second information satisfying the second condition before the expiry of the first timer, and does not receive third information from the network device before the expiry of the first timer, and all other timers have expired or stopped, it is determined that the contention resolution fails, wherein the third information is used to indicate retransmission of the first message. It can be understood that the difference between the determination of the contention resolution failure here and the case 1 (1) described above is that the terminal device does not receive the second information satisfying the second condition before the expiry of the first timer. Other related contents can be referred to the description above.

[0150] Case 2 (1), starting a timer

[0151] In some embodiments, the plurality of first messages are transmitted in an FDM manner, and a timer can be started for the plurality of first messages. In some embodiments, the plurality of first messages are transmitted within a first time window, and a timer can be started for the plurality of first messages.

[0152] In some embodiments, during the running of the timer, if the terminal device receives the first information from the network device, and the first information satisfies the first condition, it is determined that the contention resolution succeeds, and the timer is stopped. In some embodiments, when the terminal device encounters a collision in a contention environment (e.g., a plurality of terminal devices contend for uplink transmission resources), it is determined that the contention resolution succeeds, that is, the network device responds to and determines the first message sent by the terminal device, so that the terminal device can complete subsequent uplink data transmission. Since the terminal device has determined that the contention resolution succeeds, the system will stop the timer at this time. In some embodiments, the first information is a MAC PDU. Before receiving the first information, the terminal device receives first downlink information scrambled by the first sequence (e.g., PDCCH scrambled by RNTI), which indicates PDSCH reception, and the terminal device acquires the first information by decoding the MAC PDU carried by the PDSCH. The related description of the first condition can be referred to the content above.

[0153] In some embodiments, if the timer expires, it is determined that the contention resolution fails. In some embodiments, if the timer expires, and the terminal device does not receive the first information satisfying the first condition, it is determined that the contention resolution fails. Since a timer is started for the plurality of first messages, when the one timer expires, it can be determined that each of the plurality of first messages fails to be successfully resolved, that is, the first message transmission fails.

[0154] In some embodiments, upon expiry of the timer, if the terminal device has not received the third information from the network device before the expiry of the timer, it is determined that the contention resolution fails, wherein the third information is used to indicate retransmission of the first message. In some embodiments, when the terminal device has not received the retransmission instruction for the first message from the network device before the expiry of the timer, and the terminal device has not received the first information satisfying the first condition, it is determined that the contention resolution fails. In some embodiments, when the plurality of first messages fail to be successfully transmitted or received, the network device sends the third information to the terminal device, which can include instructions related to retransmission operation, to inform the terminal device that the first message needs to be retransmitted, so as to re-establish the correct communication state when there is an error or loss in communication. In some embodiments, when the terminal device has not received the retransmission instruction for the first message from the network device before the expiry of the timer, and other timers have expired or stopped, and the terminal device has not received the first information satisfying the first condition, it is determined that the contention resolution fails.

[0155] Case 2(1), start a timer

[0156] In some embodiments, upon expiry of the timer, if the terminal device has received the second information before the expiry of the timer, and the second information satisfies the second condition, it is determined that the contention resolution succeeds. In some embodiments, the second condition includes: the second information indicates receiving a PDSCH (Physical Downlink Shared Channel); the terminal device successfully decodes a MAC PDU (Medium Access Control Protocol Data Unit) carried by the PDSCH; the MAC PDU contains a contention resolution MAC CE, and the contention resolution MAC CE indicates that the contention resolution identifier matches the CCCH SDU (Common Control Channel Service Data Unit) transmitted in the first message, or matches part of the bits in the CCCH SDU transmitted in the first message. It can be understood that in this case, only the reception of the second information before the expiry of the timer is limited, and the above steps of the terminal device successfully decoding the MAC PDU carried by the PDSCH; the MAC PDU containing the contention resolution MAC CE, and the contention resolution MAC CE indicating that the contention resolution identifier matches the CCCH SDU transmitted in the first message, or matches part of the bits in the CCCH SDU transmitted in the first message are not limited to whether they are completed before the expiry of the timer. That is, the above steps can be completed before the expiry of the timer, corresponding to the above case 2(1), or the above steps can be completed after the expiry of the timer, which is not limited in the present application.

[0157] In some embodiments, upon expiry of the timer, if the terminal device does not receive the second information satisfying the second condition before the expiry of the timer, it is determined that the contention resolution fails; or, upon expiry of the timer, if the terminal device does not receive the second information satisfying the second condition before the expiry of the timer and does not receive third information from the network device before the expiry of the timer, it is determined that the contention resolution fails, wherein the third information is used to indicate retransmission of the first message. It can be understood that the difference between the determination of the contention resolution failure here and the case 2(1) described above is that the terminal device does not receive the second information satisfying the second condition before the expiry of the timer. For other related content, please refer to the description above.

[0158] Case 3(1), starting at least one timer

[0159] In some embodiments, the plurality of first messages are transmitted in a joint TDM and FDM manner, and at least one timer is started according to the time when each of the plurality of first messages is completed.

[0160] In some embodiments, during running of a first timer in the at least one timer, if the terminal device receives first information from the network device, and the first information satisfies the first condition, it is determined that the contention resolution succeeds, and the running timer is stopped, wherein the first timer is any one of the plurality of timers. It can be understood that for the case of starting at least one timer, the first timer can correspond to one first message or a plurality of first messages. In some embodiments, when it is determined that the contention resolution succeeds, i.e., the network device responds to and determines the first message sent by the terminal device, so that the terminal device can complete subsequent uplink data transmission. Since the terminal device has determined that the contention resolution succeeds, the system will stop other running timers in the at least one timer at this time. In some embodiments, the first information is a MAC PDU. Before receiving the first information, the terminal device receives first downlink information (such as PDCCH scrambled by RNTI) scrambled by the first sequence, and the PDCCH indicates PDSCH reception. The terminal device decodes the MAC PDU carried by the PDSCH to obtain the first information. For related description of the first condition, please refer to the content above.

[0161] In some embodiments, upon expiry of the first timer, if all other timers have expired or stopped, and the terminal device does not receive the first information satisfying the first condition, it is determined that the contention resolution fails; or, upon expiry of the first timer, if the terminal device does not receive third information from the network device before the expiry of the first timer, and all other timers have expired or stopped, and the terminal device does not receive the first information satisfying the first condition, it is determined that the contention resolution fails, wherein the third information is used to indicate retransmission of the first message. For other related content, please refer to the content above.

[0162] Case 3(2), starting at least one timer

[0163] In some embodiments, when a first timer of the plurality of timers expires, if the terminal device has received the second information before the expiration of the first timer, in a case that the second information satisfies a second condition, it is determined that the contention resolution is successful, and other timers that are running are stopped, the first timer being any one of the plurality of timers. In some embodiments, the second condition comprises: the second information indicates that a PDSCH (Physical Downlink Shared Channel) is received; the terminal device successfully decodes a MAC PDU (Medium Access Control Protocol Data Unit) carried by the PSDCH; the MAC PDU contains a contention resolution MAC CE, and the contention resolution MAC CE indicates that a contention resolution identifier matches the CCCH SDU (Common Control Channel Service Data Unit) transmitted in the first message, or matches part of the bits in the CCCH SDU transmitted in the first message. It can be understood that in this case, only the reception of the second information before the expiration of the timer is limited, and the steps of the terminal device successfully decoding the MAC PDU carried by the PSDCH; the MAC PDU containing the contention resolution MAC CE, and the contention resolution MAC CE indicating that the contention resolution identifier matches the CCCH SDU transmitted in the first message, or matches part of the bits in the CCCH SDU transmitted in the first message are not limited to whether they are completed before the expiration of the timer. That is, the above steps can be completed before the expiration of the timer, corresponding to the above case 3(1), and the above steps can also be completed after the expiration of the timer, which is not limited in the present application.

[0164] In some embodiments, when the first timer expires, if the terminal device has not received the second information satisfying the second condition before the expiration of the first timer, and all other timers have expired or stopped, it is determined that the contention resolution fails; or, when the first timer expires, if the terminal device has not received the second information satisfying the second condition before the expiration of the first timer, and has not received third information from the network device before the expiration of the first timer, and all other timers have expired or stopped, it is determined that the contention resolution fails, wherein the third information is used to indicate retransmission of the first message. It can be understood that the difference between the determination of the contention resolution failure here and the above case 3(1) is that the terminal device has not received the second information satisfying the second condition before the expiration of the timer. Other related contents please refer to the description above.

[0165] The above method, in the contention-based small data transmission process, the first message is Msg3, and the terminal device transmits a plurality of Msg3s, which can reduce the probability that the terminal device cannot be successfully received by the network device due to Msg3 conflict, thereby reducing the EDT delay and improving the Msg3 PUSCH capacity.

[0166] Scenario 2: Random access procedure

[0167] In some embodiments, the first message is a message in a random access procedure. In some embodiments, the first message is Msg1, and the timer is a random access response time window (RAR window). In some embodiments, the terminal device can randomly select multiple ROs to send multiple Msg1s in a TDM manner, or randomly select multiple ROs to send multiple Msg1s in a FDM manner, or randomly select multiple ROs to send multiple Msg1s in a joint TDM and FDM manner, and the preambles corresponding to the multiple Msg1s can be the same or different.

[0168] In some embodiments, the random access procedure refers to a contention-based random access procedure, as described in the background section above. For the terminal device, after sending Msg1, it also needs to receive Msg2, continue to transmit Msg3, and receive Msg4. Therefore, the way of determining the contention resolution status of the first message is different from that of the small data transmission procedure in scenario 1.

[0169] Similarly, according to the different starting modes of the timer, the contention resolution status of the terminal device is determined in the following three cases: starting multiple timers, each timer corresponding to a first message, starting one timer, and starting at least one timer.

[0170] Case 1(1): Starting multiple timers, each timer corresponding to a first message

[0171] In some embodiments, when multiple messages are sent in any one of the TDM, FDM, and joint TDM and FDM manners, multiple timers can be started, and each timer corresponds to a first message.

[0172] In some embodiments, during the running of the first timer in the multiple timers, if the terminal device receives fourth information from the network device, the second message is sent based on the fourth information, and the timer corresponding to the second message is started. The first timer is any one of the multiple timers. During the running of the timer corresponding to the second message, if the terminal device receives the first information from the network device, in the case where the first information satisfies the third condition, it is determined that the contention resolution is successful, and the running timer is stopped.

[0173] In some embodiments, stopping the running timer refers to stopping the running timer corresponding to the first message and the running timer corresponding to the second message. That is, stopping the running random access response timer corresponding to Msg1 and the running contention resolution timer corresponding to Msg3. In some embodiments, the third condition comprises: the first information contains a contention resolution MAC CE, and the contention resolution MAC CE indicates that the contention resolution identifier matches the CCCH SDU transmitted in the second message, or matches part of the bits in the CCCH SDU transmitted in the second message. For the first information, please refer to the relevant description above. In some embodiments, the fourth information refers to a random access response (RAR), that is, the response of the network device to the random access request of the terminal device. In some embodiments, after successfully receiving the RAR, the terminal device can send the second message based on the RAR to further establish a communication connection with the network device. In some embodiments, the first message is Msg1, and the timer is the random access response time window. The second message is Msg3, and the timer corresponding to the second message is the contention resolution timer. In some embodiments, the random access response time window refers to a fixed time period for determining the timing of the random access response (RAR) that the network device can send. In some embodiments, the contention resolution timer is used to determine a time period for waiting for contention resolution. When the terminal device receives the RAR, if it needs to send Msg3 to complete the communication process, it will start the contention resolution timer to determine the contention resolution within a specified time. In some embodiments, if the terminal device does not receive the fourth information from the network device during the running of all timers corresponding to the first message, that is, the network device does not respond to the first message sent by the terminal device, it is determined that the random access response reception fails. Illustratively, if the terminal device does not receive the RAR from the network device during the running of all timers corresponding to Msg1, the terminal device considers that the random access response reception fails. The terminal device updates PREAMBLE_TRANSMISSION_COUNTER, that is, PREAMBLE_TRANSMISSION_COUNTER += 1, where PREAMBLE_TRANSMISSION_COUNTER refers to a counter for recording the number of random access response reception failures. When the terminal device determines that the random access response reception fails, the terminal device will update the counter, that is, the value of the counter will increase by one.

[0174] In some embodiments, when the timer corresponding to the second message expires, if the timers corresponding to other second messages sent by the terminal device have all expired or stopped, and the terminal device does not receive the first information satisfying the third condition, it is determined that the contention resolution fails. In some embodiments, when the timer corresponding to the second message expires, if the terminal device does not receive the fifth information from the network device before the timer corresponding to the second message expires, and the timers corresponding to other second messages sent by the terminal device have all expired or stopped, and the terminal device does not receive the first information satisfying the third condition, it is determined that the contention resolution fails, wherein the fifth information is used to indicate retransmission of the second message. In some embodiments, when multiple second messages fail to be successfully transmitted or received, the network device sends the fifth information to the terminal device, which can include instructions related to retransmission operation, to inform the terminal device that the second message needs to be retransmitted, so as to re-establish the correct communication state when there is an error or loss in communication. In some embodiments, when the terminal device does not receive the retransmission instruction for the second message from the network device before the timer corresponding to the second message expires, and the timers corresponding to the second messages have all expired or stopped, and the terminal device does not receive the first information satisfying the third condition, it is determined that the contention resolution fails.

[0175] Case 1 (2), start multiple timers, each timer corresponding to a first message

[0176] In some embodiments, during running of a first timer in the multiple timers, if the terminal device receives the fourth information from the network device, the second message is sent based on the fourth information, and a timer corresponding to the second message is started, the first timer being any one of the multiple timers; when the timer corresponding to the second message expires, if the terminal device has received the second information before the timer corresponding to the second message expires, and the second information satisfies the fourth condition, it is determined that the contention resolution succeeds, and the running timers are stopped. In some embodiments, stopping the running timers means stopping the running timer corresponding to the first message and the running timer corresponding to the second message. That is, stopping the running random access response timer corresponding to Msg1 and the running contention resolution timer corresponding to Msg3.

[0177] In some embodiments, the fourth condition comprises: the second information indicates receiving the PDSCH; the terminal device successfully decodes a MAC PDU carried by the PDSCH; the MAC PDU contains a contention resolution MAC CE, and the contention resolution MAC CE indicates that a contention resolution identifier matches a CCCH SDU transmitted in the second message or matches part of the bits in the CCCH SDU transmitted in the second message. It can be understood that, in this case, only the reception of the second information before the expiration of the timer corresponding to the second message is limited to the above-mentioned steps of the terminal device successfully decoding the MAC PDU carried by the PDSCH; the MAC PDU contains the contention resolution MAC CE, and the contention resolution MAC CE indicates that the contention resolution identifier matches the CCCH SDU transmitted in the first message or matches part of the bits in the CCCH SDU transmitted in the first message, and it is not limited whether it is completed before the expiration of the timer corresponding to the second message. That is, the above-mentioned steps can be completed before the expiration of the timer corresponding to the second message, that is, corresponding to the above-mentioned case 1(1), the above-mentioned steps can also be completed after the expiration of the timer corresponding to the second message, and the present application does not limit this.

[0178] In some embodiments, when the timer corresponding to the second message expires, if the terminal device does not receive the second information satisfying the fourth condition before the expiration of the timer corresponding to the second message, and the timers corresponding to the other second messages sent by the terminal device have all expired or stopped, it is determined that the contention resolution fails; or, when the timer corresponding to the second message expires, if the terminal device does not receive the second information satisfying the fourth condition before the expiration of the timer corresponding to the second message, and does not receive fifth information from the network device before the expiration of the timer corresponding to the second message, and the timers corresponding to the other second messages sent by the terminal device have all expired or stopped, it is determined that the contention resolution fails, wherein the fifth information is used to indicate retransmission of the second message. In some embodiments, the fifth information is a PDCCH. It can be understood that the difference between the determination of the contention resolution failure here and the above-mentioned case 1(1) is that the terminal device does not receive the second information satisfying the fourth condition before the expiration of the first timer. For other related contents, please refer to the description above.

[0179] Case 2(1), starting a timer

[0180] In some embodiments, the multiple first messages are sent in an FDM manner, and then a timer can be started for the multiple first messages. In some embodiments, the multiple first messages are sent within a first time window, and then a timer can be started for the multiple first messages.

[0181] In some embodiments, during the running of the timer, if the terminal device receives fourth information from the network device, the second message is sent based on the fourth information, and a timer corresponding to the second message is started; during the running of the timer corresponding to the second message, if the terminal device receives the first information from the network device, in the case where the first information satisfies the third condition, it is determined that the contention resolution is successful, and the running timer is stopped. In some embodiments, since the terminal device has determined that the contention resolution is successful, the system will stop the timer at this time. In some embodiments, in some embodiments, the first information is a MAC PDU. Before receiving the first information, the terminal device receives first downlink information (such as RNTI scrambled PDCCH) scrambled by the first sequence, which indicates PDSCH reception, and the terminal device obtains the first information by decoding the MAC PDU carried by the PDSCH. For related description of the third condition, please refer to the foregoing content.

[0182] In some embodiments, if the timer corresponding to the second message times out, it is determined that the contention resolution fails; or, when the timer corresponding to the second message times out, if the terminal device does not receive fifth information from the network device before the timer corresponding to the second message times out, it is determined that the contention resolution fails, wherein the fifth information is used to indicate retransmission of the second message. In some embodiments, when multiple first messages fail to be successfully transmitted or received, the network device sends the fifth information to the terminal device, which can include instructions related to retransmission operation, for informing the terminal device to retransmit the second message, so as to reestablish the correct communication state when there is an error or loss in communication. In some embodiments, when the terminal device does not receive retransmission instructions for the second message from the network device before the timer corresponding to the second message times out, and other timers have timed out or stopped, and the terminal device does not receive second information satisfying the fourth condition, it is determined that the contention resolution fails.

[0183] Case 2 (2), start a timer

[0184] In some embodiments, during the running of the timer, if the terminal device receives fourth information from the network device, the second message is sent based on the fourth information, and a timer corresponding to the second message is started; when the timer corresponding to the second message expires, if the terminal device has received the second information before the expiration of the timer corresponding to the second message, and the second information satisfies the fourth condition, it is determined that the contention resolution is successful. It can be understood that in this case, only the reception of the second information before the expiration of the timer corresponding to the second message is limited, and the above terminal device successfully decodes the MAC PDU carried by the PSDCH; the MAC PDU contains the contention resolution MAC CE, and the contention resolution MAC CE indicates that the contention resolution identifier matches the CCCH SDU transmitted in the second message, or matches part of the bits in the CCCH SDU transmitted in the second message, and it is not limited whether it is completed before the expiration of the timer corresponding to the second message. That is, the above steps can be completed before the expiration of the timer corresponding to the second message, that is, corresponding to the above case 2(1), the above steps can also be completed after the expiration of the timer corresponding to the second message, and the present application does not limit this.

[0185] In some embodiments, when the timer corresponding to the second message expires, if the terminal device does not receive the second information satisfying the fourth condition before the expiration of the timer corresponding to the second message, it is determined that the contention resolution fails; or, when the timer corresponding to the second message expires, if the terminal device does not receive the second information satisfying the fourth condition before the expiration of the timer corresponding to the second message, and does not receive fifth information from the network device before the expiration of the timer corresponding to the second message, it is determined that the contention resolution fails, wherein the fifth information is used to indicate retransmission of the second message. In some embodiments, if the terminal device does not receive the fourth information from the network device during the running of the timer corresponding to the first message, it is determined that the random access response reception fails. It can be understood that the difference between determining the contention resolution failure here and the above case 2(1) is that the terminal device does not receive the second information satisfying the fourth condition before the expiration of the timer corresponding to the second message. For other related contents, please refer to the description above.

[0186] Case 3(1), starting at least one timer

[0187] In some embodiments, the plurality of first messages are sent in a joint TDM and FDM manner, and at least one timer is started according to the time when each of the plurality of first messages is completed.

[0188] In some embodiments, during the operation of a first timer among at least one timer, if the terminal device receives a fourth message from the network device, it sends a second message based on the fourth message and starts the timer corresponding to the second message. The first timer is any one of multiple timers. During the operation of the timer corresponding to the second message, if the terminal device receives a first message from the network device, and the first message satisfies a third condition, it determines that the contention resolution is successful and stops the running timer. The first timer is any one of multiple timers. In some embodiments, if the terminal device does not receive a fourth message from the network device during the operation of any of the timers corresponding to the first messages, it determines that the random access response reception has failed. In some embodiments, stopping the running timer means stopping the timer corresponding to the first message and / or the timer corresponding to the second message. That is, stopping the random access response timer corresponding to Msg1 and / or the contention resolution timer corresponding to Msg3. Please refer to the above for a description of the first message and the third condition.

[0189] In some embodiments, when the timer corresponding to the second message times out, if the timers corresponding to other second messages sent by the terminal device have all timed out or stopped, and the terminal device has not received the first information that satisfies the third condition, then the contention resolution is determined to have failed; or, when the timer corresponding to the second message times out, if the terminal device has not received the fifth information from the network device before the timer corresponding to the second message times out, and the timers corresponding to other second messages sent by the terminal device have all timed out or stopped, and the terminal device has not received the first information that satisfies the third condition, then the contention resolution is determined to have failed, wherein the fifth information is used to indicate retransmission of the second message. For other related content, please refer to the description above.

[0190] Case 3(2): Start at least one timer.

[0191] In some embodiments, during running of the first timer in the at least one timer, if the terminal device receives fourth information from the network device, the second message is sent based on the fourth information, and a timer corresponding to the second message is started, the first timer being any one of the plurality of timers; when the timer corresponding to the second message expires, if the terminal device has received the second information before the timer corresponding to the second message expires, and the second information meets the fourth condition, it is determined that the contention resolution is successful, and the running timer is stopped. In some embodiments, stopping the running timer means stopping the running timer corresponding to the first message and / or the running timer corresponding to the second message. That is, stopping the running random access response timer corresponding to Msg1 and / or the running contention resolution timer corresponding to Msg3. It can be understood that in this case, only the reception of the second information before the expiration of the timer corresponding to the second message is limited to the successful decoding of the MAC PDU carried by the PSDCH by the terminal device; the MAC PDU contains the contention resolution MAC CE, and the contention resolution MAC CE indicates that the contention resolution identifier matches the CCCH SDU transmitted in the second message, or matches part of the bits in the CCCH SDU transmitted in the second message, and it is not limited whether it is completed before the expiration of the timer corresponding to the second message. That is, the above steps can be completed before the expiration of the timer corresponding to the second message, that is, corresponding to the above case 3(1), the above steps can also be completed after the expiration of the timer corresponding to the second message, and the present application does not limit this.

[0192] In some embodiments, when the timer corresponding to the second message expires, if the terminal device does not receive the second information meeting the fourth condition before the expiration of the timer corresponding to the second message, and the timers corresponding to other second messages sent by the terminal device have all expired or stopped, it is determined that the contention resolution fails; or, when the timer corresponding to the second message expires, if the terminal device does not receive the second information meeting the fourth condition before the expiration of the timer corresponding to the second message, and does not receive fifth information from the network device before the expiration of the timer corresponding to the second message, and the timers corresponding to other second messages sent by the terminal device have all expired or stopped, it is determined that the contention resolution fails, wherein the fifth information is used to indicate retransmission of the second message. It can be understood that the difference between determining the contention resolution to fail here and the above case 3(1) is that the terminal device does not receive the second information meeting the fourth condition before the expiration of the timer. For other related contents, please refer to the description above.

[0193] In some embodiments, for the random access procedure described above, the condition that the terminal device determines that the contention resolution fails further includes that all the timers corresponding to the first messages sent by the terminal device have expired or stopped.

[0194] The method described above, in the random access procedure, the terminal device transmits multiple Msg1, which can reduce the probability of random access attempt failure of the terminal device due to Msg1 collision, thereby reducing the random access delay and improving the PRACH capacity.

[0195] Scenario 3: contention-based uplink configured grant transmission procedure

[0196] In some embodiments, the first message is a message in the contention-based uplink configured grant transmission procedure. In some embodiments, the uplink configured grant transmission procedure can refer to a procedure in which a terminal device in a connected state requests uplink data transmission resources from a network device after a random access succeeds.

[0197] Similarly, according to the different timer starting modes, the contention resolution of the terminal device is determined in the following three cases: starting multiple timers, each timer corresponding to a first message, starting one timer, and starting at least one timer.

[0198] Case 1: starting multiple timers, each timer corresponding to a first message

[0199] In some embodiments, when multiple messages are sent in any one of the TDM, FDM, and joint TDM and FDM modes, multiple timers can be started, and each timer corresponds to a first message.

[0200] In some embodiments, during the running of the first timer in the multiple timers, if the terminal device receives sixth information from the network device, it is determined that the contention resolution succeeds, and the running timer is stopped. The first timer is any one of the multiple timers. In some embodiments, the sixth information is a PDCCH scrambled by a C-RNTI. In some embodiments, the PDCCH scrambled by the C-RNTI is used to allocate and schedule uplink resources, including time-frequency resources. In some embodiments, stopping the running timer means stopping all running timers corresponding to the first messages.

[0201] In some embodiments, during running of the first timer, if the terminal device receives sixth information from the network device, and the sixth information indicates that an uplink grant for new transmission is allocated, it is determined that the contention resolution is successful, and the running timer is stopped. The first timer is any one of the plurality of timers. In some embodiments, the uplink grant for new transmission refers to an uplink resource allocated by the network device to the terminal device to support new data transmission thereof.

[0202] In some embodiments, when the first timer expires, if all the other timers have expired or stopped, it is determined that the contention resolution fails; or, when the first timer expires, if the terminal device does not receive third information from the network device before the first timer expires, and all the other timers have expired or stopped, it is determined that the contention resolution fails, wherein the third information is used to indicate retransmission of the first message. For the third information, please refer to the relevant description above.

[0203] Case 2, starting one timer

[0204] In some embodiments, the plurality of first messages are sent in an FDM manner, and one timer can be started for the plurality of first messages. In some embodiments, the plurality of first messages are sent within a first time window, and one timer can be started for the plurality of first messages.

[0205] In some embodiments, during running of the timer, if the terminal device receives sixth information from the network device, it is determined that the contention resolution is successful, and the timer is stopped; or, during running of the timer, if the terminal device receives sixth information from the network device, and the sixth information indicates that an uplink grant for new transmission is allocated, it is determined that the contention resolution is successful, and the timer is stopped.

[0206] In some embodiments, if the timer expires, it is determined that the contention resolution fails; or, when the timer expires, if the terminal device does not receive third information from the network device before the timer expires, it is determined that the contention resolution fails, wherein the third information is used to indicate retransmission of the first message. For the third information, please refer to the relevant description above.

[0207] Case 3, starting at least one timer

[0208] In some embodiments, the plurality of first messages are sent in a joint TDM and FDM manner, and at least one timer is started according to the time when each of the plurality of first messages is completed.

[0209] In some embodiments, during running of a first timer of the at least one timer, if the terminal device receives sixth information from the network device, it is determined that the contention resolution is successful, the running timer is stopped, and the first timer is any one of the plurality of timers; or, during running of a first timer of the at least one timer, if the terminal device receives sixth information from the network device, and the sixth information indicates that an uplink grant for new transmission is allocated, it is determined that the contention resolution is successful, the running timer is stopped, and the first timer is any one of the plurality of timers. In some embodiments, when the first timer expires, if all other timers have expired or stopped, it is determined that the contention resolution fails; or, when the first timer expires, if the terminal device does not receive third information from the network device before the first timer expires, and all other timers have expired or stopped, it is determined that the contention resolution fails, wherein the third information is used to indicate retransmission of the first message. For related descriptions, please refer to the foregoing content.

[0210] The above method can reduce the probability of request failure of the terminal device due to collision of the first messages, thereby ensuring transmission of uplink data of the terminal device.

[0211] The following is an apparatus embodiment of the present application, which can be used to execute the method embodiments of the present application. For details not disclosed in the apparatus embodiments of the present application, please refer to the method embodiments of the present application.

[0212] Please refer to FIG. 8, which shows a block diagram of a wireless communication apparatus according to an embodiment of the present application. The apparatus has functions of implementing the above wireless communication method, which can be implemented by hardware or by execution of corresponding software by hardware. The apparatus can be the terminal device introduced above or can be arranged in the terminal device. As shown in FIG. 8, the apparatus 800 can include a sending module 810 and a processing module 820.

[0213] The sending module 810 is configured to send a plurality of first messages.

[0214] The processing module 820 is configured to start at least one timer for the plurality of first messages.

[0215] The processing module 820 is further configured to monitor downlink information from the network device during running of the timer.

[0216] In some embodiments, the plurality of first messages are sent in a time division multiplexing (TDM) manner; and the processing module 820 is configured to start a plurality of timers for the plurality of first messages, each timer corresponding to one first message.

[0217] In some embodiments, the multiple first messages are transmitted in a frequency division multiplexing (FDM) manner; the processing module 820 is configured to start multiple timers for the multiple first messages, each timer corresponding to one first message; or start one timer for the multiple first messages.

[0218] In some embodiments, the multiple first messages are transmitted in a joint TDM and FDM manner; the processing module 820 is configured to start multiple timers for the multiple first messages, each timer corresponding to one first message; or start at least one timer according to the time when each of the multiple first messages is completed.

[0219] In some embodiments, the processing module 820 is configured to start a timer each time a first message is completed; or start a timer at a first interval after each time a first message is completed, the first interval being determined based on a round trip time between the terminal device and the network device.

[0220] In some embodiments, the processing module 820 is configured to start a timer when the multiple first messages are completed if the multiple first messages are completed at the same time; or start a timer at a first interval after the multiple first messages are completed if the multiple first messages are completed at the same time; or start a timer when a target first message is completed if the multiple first messages are not completed at the same time; or start a timer at a first interval after a target first message is completed if the multiple first messages are not completed at the same time; wherein the target first message is the first message that is completed earliest among the multiple first messages, or the target first message is the first message that is completed latest among the multiple first messages, and the first interval is determined based on a round trip time between the terminal device and the network device.

[0221] In some embodiments, the processing module 820 is configured to start a timer for each first message of the multiple first messages that is completed at a different time; and start a timer for each first message of the multiple first messages that is completed at the same time.

[0222] In some embodiments, the multiple first messages are completed within a first time window; and the processing module 820 is configured to start one timer for the multiple first messages.

[0223] In some embodiments, the starting moment of the timer is determined based on an ending moment of the first time window; or the starting moment of the timer is determined based on the ending moment of the first time window and a first interval duration, the first interval duration being determined based on a round trip time between the terminal device and the network device.

[0224] In some embodiments, the processing module 820 is configured to monitor the first downlink channel scrambled by the first sequence during running of the timer; wherein the first sequence is associated with the terminal device, or the first sequence is associated with the transmission resource of the first message.

[0225] In some embodiments, the first message is a message in a random access procedure, or a message in a contention-based small data transmission procedure, or a message in a contention-based uplink configured grant transmission procedure.

[0226] In some embodiments, in a case where multiple timers are started, each corresponding to a first message, the processing module 820 is configured to, during running of a first timer in the multiple timers, stop the first timer if the terminal device receives first information from the network device, the first timer being any one of the multiple timers; and in a case where the first information satisfies a first condition, determine that contention resolution is successful, and stop other timers that are running.

[0227] In some embodiments, the processing module 820 is configured to, when the first timer expires, determine that contention resolution fails if other timers have all expired or stopped, and the terminal device has not received first information satisfying the first condition; or, when the first timer expires, determine that contention resolution fails if the terminal device has not received third information from the network device before the first timer expires, and other timers have all expired or stopped, and the terminal device has not received first information satisfying the first condition, wherein the third information is used to indicate retransmission of the first message.

[0228] In some embodiments, in a case where multiple timers are started, each corresponding to a first message, the processing module 820 is configured to, when a first timer in the multiple timers expires, determine that contention resolution is successful if the terminal device has received second information before the first timer expires, and in a case where the second information satisfies a second condition, stop other timers that are running, the first timer being any one of the multiple timers.

[0229] In some embodiments, the processing module 820 is configured to, in a case where a timer is started, determine that contention resolution is successful if the terminal device receives first information from the network device during running of the timer, and the first information satisfies a first condition, and stop the timer.

[0230] In some embodiments, in a case where a timer is started, the processing module 820 is configured to, during running of the timer, determine that contention resolution is successful if the terminal device receives first information from the network device, and the first information satisfies a first condition, and stop the timer.

[0231] In some embodiments, the processing module 820 is configured to, if the timer expires, determine that contention resolution fails; or, if the terminal device does not receive third information from the network device before the timer expires, determine that contention resolution fails when the timer expires, wherein the third information is used to indicate retransmission of the first message.

[0232] In some embodiments, in a case where a timer is started, the processing module 820 is configured to, if the terminal device receives second information before the timer expires, determine that contention resolution is successful if the second information satisfies a second condition when the timer expires.

[0233] In some embodiments, the processing module 820 is configured to, if the terminal device does not receive second information satisfying the second condition before the timer expires, determine that contention resolution fails when the timer expires; or, if the terminal device does not receive second information satisfying the second condition before the timer expires, and does not receive third information from the network device before the timer expires, determine that contention resolution fails when the timer expires, wherein the third information is used to indicate retransmission of the first message.

[0234] In some embodiments, in a case where at least one timer is started, the processing module 820 is configured to, during running of a first timer of the at least one timer, determine that contention resolution is successful if the terminal device receives first information from the network device, and the first information satisfies a first condition, and stop the running timer, the first timer being any one of the plurality of timers.

[0235] In some embodiments, the processing module 820 is configured to, when the first timer expires, if all other timers have expired or stopped, and the terminal device does not receive the first information satisfying the first condition, determine that the contention resolution fails; or, when the first timer expires, if the terminal device does not receive the third information from the network device before the first timer expires, and all other timers have expired or stopped, and the terminal device does not receive the first information satisfying the first condition, determine that the contention resolution fails, wherein the third information is used to instruct to retransmit the first message.

[0236] In some embodiments, when at least one timer is started, the processing module 820 is configured to, when a first timer of the plurality of timers expires, if the terminal device has received the second information before the first timer expires, and the second information satisfies a second condition, determine that the contention resolution succeeds, and stop other timers that are running, wherein the first timer is any one of the plurality of timers.

[0237] In some embodiments, the processing module 820 is configured to, when the first timer expires, if the terminal device does not receive the second information satisfying the second condition before the first timer expires, and all other timers have expired or stopped, determine that the contention resolution fails; or, when the first timer expires, if the terminal device does not receive the second information satisfying the second condition before the first timer expires, and does not receive the third information from the network device before the first timer expires, and all other timers have expired or stopped, determine that the contention resolution fails, wherein the third information is used to instruct to retransmit the first message.

[0238] In some embodiments, the first condition comprises that the first information contains a contention resolution medium access control layer control element (MAC CE), and the contention resolution MAC CE indicates a contention resolution identity that matches a common control channel service data unit (CCCH SDU) transmitted in the first message, or matches part of bits in the CCCH SDU transmitted in the first message.

[0239] In some embodiments, the second condition comprises: the second information indicates receiving a physical downlink shared channel (PDSCH); the terminal device successfully decodes a medium access control (MAC) protocol data unit (PDU) carried by the PDSCH; the MAC PDU contains a contention resolution MAC CE, and the contention resolution MAC CE indicates a contention resolution identity matching the CCCH SDU transmitted in the first message, or matching part of bits in the CCCH SDU transmitted in the first message.

[0240] In some embodiments, the first message is Msg3, and the timer is a contention resolution timer.

[0241] In some embodiments, in a case where a plurality of timers are started, each corresponding to a first message, the processing module 820 is configured to, during running of a first timer in the plurality of timers, if the terminal device receives fourth information from the network device, send a second message based on the fourth information, and start a timer corresponding to the second message, the first timer being any one of the plurality of timers; during running of the timer corresponding to the second message, if the terminal device receives the first information from the network device, and the first information satisfies a third condition, determine that contention resolution is successful, and stop the running timer.

[0242] In some embodiments, the processing module 820 is configured to, when the timer corresponding to the second message times out, if timers corresponding to other second messages sent by the terminal device have all timed out or stopped, and the terminal device has not received the first information satisfying the third condition, determine that contention resolution fails; or, when the timer corresponding to the second message times out, if the terminal device has not received fifth information from the network device before the timer corresponding to the second message times out, and timers corresponding to other second messages sent by the terminal device have all timed out or stopped, and the terminal device has not received the first information satisfying the third condition, determine that contention resolution fails, wherein the fifth information is used to indicate retransmitting the second message.

[0243] In some embodiments, in a case where a plurality of timers are started, each corresponding to a first message, the processing module 820 is configured to, during running of a first timer in the plurality of timers, if the terminal device receives fourth information from the network device, send a second message based on the fourth information, and start a timer corresponding to the second message, the first timer being any one of the plurality of timers; and in a case where the timer corresponding to the second message expires, if the terminal device has received second information before the timer corresponding to the second message expires, and the second information satisfies a fourth condition, determine that contention resolution is successful, and stop the running timer.

[0244] In some embodiments, the processing module 820 is configured to, in a case where the timer corresponding to the second message expires, if the terminal device has not received second information satisfying the fourth condition before the timer corresponding to the second message expires, and timers corresponding to other second messages sent by the terminal device have all expired or stopped, determine that contention resolution fails; or, in a case where the timer corresponding to the second message expires, if the terminal device has not received second information satisfying the fourth condition before the timer corresponding to the second message expires, and has not received fifth information from the network device before the timer corresponding to the second message expires, and timers corresponding to other second messages sent by the terminal device have all expired or stopped, determine that contention resolution fails, wherein the fifth information is used to indicate retransmission of the second message.

[0245] In some embodiments, the processing module 820 is configured to, if the terminal device does not receive fourth information from the network device during running of all timers corresponding to first messages, determine that reception of a random access response fails.

[0246] In some embodiments, in a case where one timer is started, the processing module 820 is configured to, during running of the timer, if the terminal device receives fourth information from the network device, send a second message based on the fourth information, and start a timer corresponding to the second message; and during running of the timer corresponding to the second message, if the terminal device receives first information from the network device, in a case where the first information satisfies a third condition, determine that contention resolution is successful, and stop the running timer.

[0247] In some embodiments, the processing module 820 is configured to determine that the contention resolution fails if the timer corresponding to the second message expires; or, when the timer corresponding to the second message expires, determine that the contention resolution fails if the terminal device does not receive fifth information from the network device before the timer corresponding to the second message expires, wherein the fifth information is used to instruct to retransmit the second message.

[0248] In some embodiments, when starting a timer, the processing module 820 is configured to, during running of the timer, if the terminal device receives fourth information from the network device, send a second message based on the fourth information and start a timer corresponding to the second message; when the timer corresponding to the second message expires, if the terminal device has received the second information before the timer corresponding to the second message expires, determine that the contention resolution succeeds in a case that the second information satisfies a fourth condition.

[0249] The processing module 820 is configured to, when the timer corresponding to the second message expires, determine that the contention resolution fails if the terminal device does not receive the second information satisfying the fourth condition before the timer corresponding to the second message expires; or, when the timer corresponding to the second message expires, determine that the contention resolution fails if the terminal device does not receive the second information satisfying the fourth condition before the timer corresponding to the second message expires and does not receive fifth information from the network device before the timer corresponding to the second message expires, wherein the fifth information is used to instruct to retransmit the second message.

[0250] In some embodiments, the processing module 820 is configured to determine that the random access response reception fails if the terminal device does not receive the fourth information from the network device during running of the timer corresponding to the first message.

[0251] In some embodiments, when starting at least one timer, the processing module 820 is configured to, during running of a first timer of the at least one timer, if the terminal device receives fourth information from the network device, send a second message based on the fourth information and start a timer corresponding to the second message, the first timer being any one of the plurality of timers; during running of the timer corresponding to the second message, if the terminal device receives first information from the network device, determine that the contention resolution succeeds in a case that the first information satisfies a third condition, stop the running timer, the first timer being any one of the plurality of timers.

[0252] In some embodiments, the processing module 820 is configured to, when the timer corresponding to the second message expires, if all the timers corresponding to the second messages sent by the terminal device have expired or stopped, and the terminal device does not receive the first information satisfying the third condition, determine that the contention resolution fails; or, when the timer corresponding to the second message expires, if the terminal device does not receive the fifth information from the network device before the timer corresponding to the second message expires, and all the timers corresponding to the second messages sent by the terminal device have expired or stopped, and the terminal device does not receive the first information satisfying the third condition, determine that the contention resolution fails, wherein the fifth information is used to instruct to retransmit the second message.

[0253] In some embodiments, when starting at least one timer, the processing module 820 is configured to, during running of a first timer in the at least one timer, if the terminal device receives the fourth information from the network device, send a second message based on the fourth information and start a timer corresponding to the second message, the first timer being any one of the plurality of timers; when the timer corresponding to the second message expires, if the terminal device has received the second information before the timer corresponding to the second message expires, and the second information satisfies a fourth condition, determine that the contention resolution succeeds, and stop the running timer.

[0254] In some embodiments, the processing module 820 is configured to, when the timer corresponding to the second message expires, if the terminal device does not receive the second information satisfying the fourth condition before the timer corresponding to the second message expires, and all the timers corresponding to the second messages sent by the terminal device have expired or stopped, determine that the contention resolution fails; or, when the timer corresponding to the second message expires, if the terminal device does not receive the second information satisfying the fourth condition before the timer corresponding to the second message expires, and does not receive the fifth information from the network device before the timer corresponding to the second message expires, and all the timers corresponding to the second messages sent by the terminal device have expired or stopped, determine that the contention resolution fails, wherein the fifth information is used to instruct to retransmit the second message.

[0255] In some embodiments, the processing module 820 is configured to, if the terminal device does not receive the fourth information from the network device during running of all the timers corresponding to the first messages, determine that the random access response reception fails.

[0256] In some embodiments, the condition for the terminal device to determine that the contention resolution fails further includes that all the timers corresponding to the first messages sent by the terminal device have expired or stopped.

[0257] In some embodiments, the third condition comprises: the first information contains a contention resolution MAC CE, and the contention resolution MAC CE indicates a contention resolution identity matching a CCCH SDU transmitted in the second message, or matching part of bits in the CCCH SDU transmitted in the second message.

[0258] In some embodiments, the fourth condition comprises: the second information indicates receiving a PDSCH; the terminal device successfully decodes a MAC PDU carried by the PSDCH; the MAC PDU contains a contention resolution MAC CE, and the contention resolution MAC CE indicates a contention resolution identity matching a CCCH SDU transmitted in the second message, or matching part of bits in the CCCH SDU transmitted in the second message.

[0259] In some embodiments, the first message is Msg1, and the timer is a random access response time window.

[0260] In some embodiments, the second message is Msg3, and the timer corresponding to the second message is a contention resolution timer.

[0261] In some embodiments, in the case where a plurality of timers are started, each corresponding to a first message, the processing module 820 is configured to determine that contention resolution is successful, and stop a running timer, if the terminal device receives sixth information from the network device during running of a first timer of the plurality of timers, the first timer being any one of the plurality of timers; or, determine that contention resolution is successful, and stop a running timer, if the terminal device receives sixth information from the network device during running of a first timer of the plurality of timers, and the sixth information indicates that an uplink grant for new transmission is allocated, the first timer being any one of the plurality of timers.

[0262] In some embodiments, the processing module 820 is configured to determine that contention resolution fails, if all other timers have timed out or stopped, when the first timer times out; or, determine that contention resolution fails, if the terminal device has not received third information from the network device before the first timer times out, and all other timers have timed out or stopped, when the first timer times out, the third information being used to indicate retransmission of the first message.

[0263] In some embodiments, the processing module 820 is configured to, in a case that a timer is started, determine that contention resolution is successful if the terminal device receives sixth information from the network device during running of the timer, and stop the timer; or, in a case that a timer is started, determine that contention resolution is successful if the terminal device receives sixth information from the network device during running of the timer, and the sixth information indicates that an uplink grant for new transmission is allocated, and stop the timer.

[0264] In some embodiments, the processing module 820 is configured to, if the timer expires, determine that contention resolution fails; or, if the terminal device does not receive third information from the network device before the timer expires, determine that contention resolution fails, wherein the third information is used to indicate retransmission of the first message.

[0265] In some embodiments, in a case that at least one timer is started, the processing module 820 is configured to, during running of a first timer of the at least one timer, determine that contention resolution is successful if the terminal device receives sixth information from the network device, and stop the running timer, wherein the first timer is any one of the multiple timers; or, during running of a first timer of the at least one timer, determine that contention resolution is successful if the terminal device receives sixth information from the network device, and the sixth information indicates that an uplink grant for new transmission is allocated, and stop the running timer, wherein the first timer is any one of the multiple timers.

[0266] In some embodiments, the processing module 820 is configured to, if the first timer expires, determine that contention resolution fails if all other timers have expired or stopped; or, if the first timer expires, determine that contention resolution fails if the terminal device does not receive third information from the network device before the first timer expires, and all other timers have expired or stopped, wherein the third information is used to indicate retransmission of the first message.

[0267] In some embodiments, the sixth information is a physical downlink control channel (PDCCH) scrambled by a cell-radio network temporary identifier (C-RNTI).

[0268] In some embodiments, the multiple first messages contain the same content.

[0269] In some embodiments, the number of the first messages is configured by the network device, or determined by the terminal device based on a maximum number configured by the network device.

[0270] It should be noted that the apparatus provided by the above embodiments is only exemplified by the above division of various functional modules when realizing its functions, and in actual application, the above functions can be completed by different functional modules according to actual needs, that is, the content structure of the device is divided into different functional modules to complete all or part of the above-described functions.

[0271] As to the apparatus in the above embodiments, the specific manners in which various modules perform operations have been described in detail in the embodiments of the method, and will not be described here in detail. For details not described in the apparatus embodiments, refer to the above method embodiments.

[0272] Please refer to FIG. 9, which shows a structural schematic diagram of a terminal device provided by an embodiment of the present application. The terminal device 900 can include a processor 901, a transceiver 902, and a memory 903. The processor 901 is configured to implement various processing functions of the terminal device 900, such as generating information to be sent, processing received information, controlling sending and / or receiving, etc., such as implementing the functions of the above processing modules. The transceiver 902 is configured to implement the functions of sending and / or receiving, such as implementing the functions of the above sending modules.

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

[0274] The transceiver 902 can include a receiver and a transmitter, for example, which can be implemented as the same wireless communication component, which can include a wireless communication chip and a radio frequency antenna.

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

[0276] The memory 903 can be used to store computer programs executed by the processor. The processor 901 is configured to execute the computer programs to implement various steps in the above method embodiments.

[0277] In some embodiments, the transceiver 902 is configured to send a plurality of first messages; the processor 901 is configured to start at least one timer for the plurality of first messages; and monitor downlink information from a network device during the running of the timer.

[0278] For details not described in the present embodiment, refer to the above embodiments, which will not be described here one by one.

[0279] In addition, the memory can be implemented by any type of volatile or nonvolatile storage devices or a combination thereof, including but not limited to: magnetic or optical disks, electrically erasable programmable read-only memories, erasable programmable read-only memories, static random access memories, read-only memories, magnetic memories, flash memories, programmable read-only memories.

[0280] The embodiment of the present application further provides a computer readable storage medium, the storage medium stores a computer program, and the computer program is used for being executed by a processor to realize the wireless communication method. In some embodiments, the computer readable storage medium can include a ROM (Read-Only Memory), a RAM (Random-Access Memory), a SSD (Solid State Drives) or an optical disc, etc. Wherein, the random access memory can include a ReRAM (Resistance Random Access Memory) and a DRAM (Dynamic Random Access Memory).

[0281] The embodiment of the present application further provides a chip, the chip includes a programmable logic circuit and / or program instructions, when the chip is running, is used for realizing the wireless communication method.

[0282] The embodiment of the present application further provides a computer program product, the computer program product includes computer instructions, the computer instructions are stored in a computer readable storage medium, and a processor reads and executes the computer instructions from the computer readable storage medium to realize the wireless communication method.

[0283] It should be understood that the "indication" mentioned in the embodiments of the present application can be direct indication, or indirect indication, or can be an indication with an associated relationship. For example, A indicates B, which can mean that A directly indicates B, for example, B can be obtained through A; or A indirectly indicates B, for example, A indicates C, and B can be obtained through C; or A and B have an associated relationship.

[0284] In the description of the embodiments of the present application, the term "corresponding" can mean that there is a direct or indirect corresponding relationship between the two, or can mean that there is an associated relationship between the two, or can mean an indication and being indicated, configuration and being configured, etc.

[0285] In some embodiments of the present application, the "predefined" can be realized by pre-storing corresponding codes, tables or other means for indicating relevant information in devices (for example, including terminal devices and network devices), and the present application does not limit the specific implementation manner thereof. For example, the predefined can refer to the definition in a protocol.

[0286] In some embodiments of the present application, the "protocol" can refer to a standard protocol in the communication field, for example, can include a BLE protocol, a Wi-Fi protocol and a relevant protocol applied to a future communication system, and the present application does not limit this.

[0287] "Multiple" mentioned in the present document refers to two or more than two. "And / or" describes the association relationship of associated objects, which means that there can be three relationships, for example, A and / or B can mean that there are three cases of A alone, A and B together, and B alone. The character " / " generally represents that the associated objects before and after it are in an "or" relationship.

[0288] "Greater than or equal to" mentioned in the present document can mean greater than or equal to, and "less than or equal to" can mean less than or equal to.

[0289] In addition, the step numbers described in the present document only exemplarily show a possible execution order between steps, and in some other embodiments, the above steps can also be executed in a sequence different from the numbers, for example, two steps with different numbers are executed at the same time, or two steps with different numbers are executed in an order opposite to the illustration, and the embodiments of the present application do not limit this.

[0290] Those skilled in the art should realize that in one or more of the above examples, the functions described in the embodiments of the present application can be realized by hardware, software, firmware or any combination thereof. When realized by software, these functions can be stored in a computer readable medium or transmitted as one or more instructions or codes on a computer readable medium. The computer readable medium includes a computer storage medium and a communication medium, wherein the communication medium includes any medium facilitating the transmission of computer programs from one place to another. The storage medium can be any available medium accessible by a general or special purpose computer.

[0291] The above only describes exemplary embodiments of the present application, and does not limit the present application, and any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method of wireless communication, the method comprising: The method is performed by a terminal device, and the method comprises: sending a plurality of first messages; starting at least one timer for the plurality of first messages; monitoring downlink information from a network device during running of the timer.

2. The method of claim 1, wherein, The plurality of first messages are sent in a time division multiplexing (TDM) manner. The step of starting at least one timer for the plurality of first messages comprises: starting a plurality of timers for the plurality of first messages, each timer corresponding to one first message.

3. The method of claim 1, wherein, The plurality of first messages are sent in a frequency division multiplexing (FDM) manner. The step of starting at least one timer for the plurality of first messages comprises: starting a plurality of timers for the plurality of first messages, each timer corresponding to one first message; or starting one timer for the plurality of first messages.

4. The method of claim 1, wherein, The plurality of first messages are sent in a joint TDM and FDM manner. The step of starting at least one timer for the plurality of first messages comprises: starting a plurality of timers for the plurality of first messages, each timer corresponding to one first message; or starting at least one timer according to a time at which each of the plurality of first messages is completed to be sent.

5. The method according to any one of claims 2 to 4, characterized in that, The step of starting a plurality of timers for the plurality of first messages comprises: starting one timer each time one first message is completed to be sent; or starting one timer at a first interval after each time one first message is completed to be sent, the first interval being determined based on a round-trip time between the terminal device and the network device.

6. The method of claim 3, wherein, The step of starting one timer for the plurality of first messages comprises: in a case where the plurality of first messages are completed to be sent at the same time, starting one timer at a time at which the plurality of first messages are completed to be sent; or in a case where the plurality of first messages are completed to be sent at the same time, starting one timer at a first interval after the plurality of first messages are completed to be sent; or in a case where the plurality of first messages are not completed to be sent at the same time, starting one timer at a time at which a target first message among the plurality of first messages is completed to be sent; or in a case where the plurality of first messages are not completed to be sent at the same time, starting one timer at a first interval after a target first message among the plurality of first messages is completed to be sent; wherein the target first message is a first message that is completed to be sent earliest among the plurality of first messages, or the target first message is a first message that is completed to be sent latest among the plurality of first messages, and the first interval is determined based on a round-trip time between the terminal device and the network device.

7. The method of claim 4, wherein, The step of starting at least one timer according to a time at which each of the plurality of first messages is completed to be sent comprises: starting one timer for each first message among the plurality of first messages that is completed to be sent at a different time; starting one timer for each first message among the plurality of first messages that is completed to be sent at the same time.

8. The method of claim 1, wherein, The plurality of first messages are completed to be sent within a first time window. The step of starting at least one timer for the plurality of first messages comprises: starting one timer for the plurality of first messages.

9. The method of claim 8, wherein the starting time of the timer is determined based on an ending time of the first time window; or the starting time of the timer is determined based on the ending time of the first time window and a first interval, the first interval being determined based on a round trip time between the terminal device and the network device. The monitoring of the downlink information from the network device during the running of the timer comprises: monitoring a first downlink channel scrambled by a first sequence during the running of the timer; wherein the first sequence is associated with the terminal device, or the first sequence is associated with a transmission resource of the first message.

10. The method according to any one of claims 1 to 9, characterized in that, The first message is a message in a random access procedure, or a message in a contention-based small data transmission procedure, or a message in a contention-based uplink configured grant transmission procedure. In a case where multiple timers are started, each corresponding to a first message, the method further comprises: stopping a first timer among the multiple timers during the running of the first timer, if the terminal device receives first information from the network device, the first timer being any one of the multiple timers; 11. The method according to any one of claims 1 to 10, characterized in that, in a case where the first information satisfies a first condition, determining that contention resolution is successful, and stopping other timers that are running.

12. The method according to any one of claims 1 to 10, characterized in that, The method further comprises: in a case where the first timer times out, if other timers have all timed out or stopped, and the terminal device does not receive first information that satisfies the first condition, determining that contention resolution fails; or, 13. The method of claim 12, wherein, in a case where the first timer times out, if the terminal device does not receive third information from the network device before the first timer times out, and other timers have all timed out or stopped, and the terminal device does not receive first information that satisfies the first condition, determining that contention resolution fails, wherein the third information is used to indicate retransmission of the first message. In a case where multiple timers are started, each corresponding to a first message, the method further comprises: in a case where a first timer among the multiple timers times out, if the terminal device has received second information before the first timer times out, and in a case where the second information satisfies a second condition, determining that contention resolution is successful, and stopping other timers that are running, the first timer being any one of the multiple timers. The method further comprises:

14. The method according to any one of claims 1 to 10, characterized in that, in a case where the first timer times out, if the terminal device does not receive second information that satisfies the second condition before the first timer times out, and other timers have all timed out or stopped, determining that contention resolution fails; or, 15. The method of claim 14, wherein, in a case where the first timer times out, if the terminal device does not receive second information that satisfies the second condition before the first timer times out, and does not receive third information from the network device before the first timer times out, and other timers have all timed out or stopped, determining that contention resolution fails, wherein the third information is used to indicate retransmission of the first message. ​ ​ ​ 16. The method according to any one of claims 1 to 10, characterized in that, In the case of starting a timer, the method further comprises: During running of the timer, if the terminal device receives first information from the network device, in the case that the first information satisfies a first condition, determining that contention resolution is successful, and stopping the timer.

17. The method of claim 16, wherein, The method further comprises: If the timer expires, determining that contention resolution fails; Or, In the case that the timer expires, if the terminal device does not receive third information from the network device before the timer expires, determining that contention resolution fails, wherein the third information is used to instruct retransmission of the first message.

18. The method according to any one of claims 1 to 10, characterized in that, In the case of starting a timer, the method further comprises: In the case that the timer expires, if the terminal device has received second information before the timer expires, in the case that the second information satisfies a second condition, determining that contention resolution is successful.

19. The method of claim 18, wherein, The method further comprises: In the case that the timer expires, if the terminal device does not receive second information satisfying the second condition before the timer expires, determining that contention resolution fails; Or, In the case that the timer expires, if the terminal device does not receive second information satisfying the second condition before the timer expires, and does not receive third information from the network device before the timer expires, determining that contention resolution fails, wherein the third information is used to instruct retransmission of the first message.

20. The method according to any one of claims 1 to 10, characterized in that, In the case of starting at least one timer, the method further comprises: During running of a first timer in the at least one timer, if the terminal device receives first information from the network device, in the case that the first information satisfies a first condition, determining that contention resolution is successful, and stopping the running timer, the first timer being any one of the plurality of timers.

21. The method of claim 20, wherein, The method further comprises: In the case that the first timer expires, if all other timers have expired or stopped, and the terminal device does not receive first information satisfying the first condition, determining that contention resolution fails; Or, In the case that the first timer expires, if the terminal device does not receive third information from the network device before the first timer expires, and all other timers have expired or stopped, and the terminal device does not receive first information satisfying the first condition, determining that contention resolution fails, wherein the third information is used to instruct retransmission of the first message.

22. The method according to any one of claims 1 to 10, characterized in that, In the case of starting at least one timer, the method further comprises: In the case that a first timer in the plurality of timers expires, if the terminal device has received second information before the first timer expires, in the case that the second information satisfies a second condition, determining that contention resolution is successful, and stopping the running other timers, the first timer being any one of the plurality of timers.

23. The method of claim 22, wherein, The method further comprises: In the case that the first timer expires, if the terminal device does not receive second information satisfying the second condition before the first timer expires, and all other timers have expired or stopped, determining that contention resolution fails; Or, when the first timer expires, if the terminal device does not receive second information satisfying the second condition before the first timer expires, and does not receive third information from the network device before the first timer expires, and all other timers have expired or stopped, it is determined that contention resolution fails, wherein the third information is used to indicate retransmission of the first message.

24. The method of any one of claims 12-13, 16-17, 20-21, wherein, The first condition includes that the first information contains a contention resolution medium access control layer control element (MAC CE), and the contention resolution MAC CE indicates a contention resolution identifier matching a common control channel service data unit (CCCH SDU) transmitted in the first message, or matching part of bits in the CCCH SDU transmitted in the first message.

25. The method of any one of claims 14-15, 18-19, 22-23, wherein, The second condition includes: The second information indicates reception of a physical downlink shared channel (PDSCH); The terminal device successfully decodes a medium access control layer protocol data unit (MAC PDU) carried by the PSDCH; The MAC PDU contains a contention resolution MAC CE, and the contention resolution MAC CE indicates a contention resolution identifier matching a CCCH SDU transmitted in the first message, or matching part of bits in the CCCH SDU transmitted in the first message.

26. The method according to any one of claims 12 to 25, characterized in that, The first message is Msg3, and the timer is a contention resolution timer.

27. The method according to any one of claims 1 to 10, characterized in that, In the case of starting multiple timers, each corresponding to a first message, the method further includes: During running of a first timer in the multiple timers, if the terminal device receives fourth information from the network device, a second message is sent based on the fourth information, and a timer corresponding to the second message is started, the first timer being any one of the multiple timers; During running of the timer corresponding to the second message, if the terminal device receives first information from the network device, and the first information satisfies a third condition, it is determined that contention resolution is successful, and the running timer is stopped.

28. The method of claim 27, wherein, The method further includes: When the timer corresponding to the second message expires, if all timers corresponding to other second messages sent by the terminal device have expired or stopped, and the terminal device does not receive first information satisfying the third condition, it is determined that contention resolution fails; Or, When the timer corresponding to the second message expires, if the terminal device does not receive fifth information from the network device before the timer corresponding to the second message expires, and all timers corresponding to other second messages sent by the terminal device have expired or stopped, and the terminal device does not receive first information satisfying the third condition, it is determined that contention resolution fails, wherein the fifth information is used to indicate retransmission of the second message.

29. The method according to any one of claims 1 to 10, characterized in that, In the case of starting multiple timers, each corresponding to a first message, the method further includes: if the terminal device receives fourth information from the network device during running of a first timer, the first timer being any one of the plurality of timers, the terminal device sends a second message based on the fourth information and starts a timer corresponding to the second message; if the terminal device receives second information before the timer corresponding to the second message expires, and the second information satisfies a fourth condition, the terminal device determines that contention resolution is successful, and stops the running timer.

30. The method of claim 29, wherein, The method further includes: if the terminal device does not receive second information satisfying the fourth condition before the timer corresponding to the second message expires, and timers corresponding to other second messages sent by the terminal device have all expired or stopped, the terminal device determines that contention resolution fails. Alternatively, if the terminal device does not receive second information satisfying the fourth condition before the timer corresponding to the second message expires, and the terminal device does not receive fifth information from the network device before the timer corresponding to the second message expires, and timers corresponding to other second messages sent by the terminal device have all expired or stopped, the terminal device determines that contention resolution fails, wherein the fifth information is used to instruct retransmission of the second message. The method further includes:

31. The method according to any one of claims 27 to 30, characterized in that, if the terminal device does not receive fourth information from the network device during running of all timers corresponding to first messages, the terminal device determines that reception of a random access response fails. In the case of starting one timer, the method further includes:

32. The method according to any one of claims 1 to 10, characterized in that, if the terminal device receives fourth information from the network device during running of the timer, the terminal device sends a second message based on the fourth information and starts a timer corresponding to the second message; if the terminal device receives first information from the network device during running of the timer corresponding to the second message, and the first information satisfies a third condition, the terminal device determines that contention resolution is successful, and stops the running timer. The method further includes:

33. The method of claim 32, wherein, if the timer corresponding to the second message expires, the terminal device determines that contention resolution fails; Alternatively, if the terminal device does not receive fifth information from the network device before the timer corresponding to the second message expires, the terminal device determines that contention resolution fails, wherein the fifth information is used to instruct retransmission of the second message. In the case of starting one timer, the method further includes:

34. The method according to any one of claims 1 to 10, characterized in that, if the terminal device receives fourth information from the network device during running of the timer, the terminal device sends a second message based on the fourth information and starts a timer corresponding to the second message; if the terminal device receives second information before the timer corresponding to the second message expires, and the second information satisfies a fourth condition, the terminal device determines that contention resolution is successful. The method further includes:

35. The method of claim 34, wherein, ​ if the terminal device does not receive the second information satisfying the fourth condition before the timer corresponding to the second message expires, it is determined that the contention resolution fails; or, if the terminal device does not receive the second information satisfying the fourth condition before the timer corresponding to the second message expires, and does not receive fifth information from the network device before the timer corresponding to the second message expires, it is determined that the contention resolution fails, wherein the fifth information is used to indicate retransmission of the second message.

36. The method of any one of claims 32 to 35, wherein, The method further comprises: if the terminal device does not receive fourth information from the network device during running of the timer corresponding to the first message, it is determined that the random access response reception fails.

37. The method according to any one of claims 1 to 10, characterized in that, In the case of starting at least one timer, the method further comprises: if the terminal device receives fourth information from the network device during running of a first timer in the at least one timer, the second message is sent based on the fourth information, and a timer corresponding to the second message is started, the first timer being any one of the plurality of timers; if the terminal device receives first information from the network device during running of the timer corresponding to the second message, and the first information satisfies a third condition, it is determined that the contention resolution succeeds, and the running timer is stopped, the first timer being any one of the plurality of timers.

38. The method of claim 37, wherein, The method further comprises: if all timers corresponding to other second messages sent by the terminal device have expired or stopped, and the terminal device does not receive first information satisfying the third condition, it is determined that the contention resolution fails when the timer corresponding to the second message expires; or, if the terminal device does not receive fifth information from the network device before the timer corresponding to the second message expires, and all timers corresponding to other second messages sent by the terminal device have expired or stopped, and the terminal device does not receive first information satisfying the third condition, it is determined that the contention resolution fails when the timer corresponding to the second message expires, wherein the fifth information is used to indicate retransmission of the second message.

39. The method according to any one of claims 1 to 10, characterized in that, In the case of starting at least one timer, the method further comprises: if the terminal device receives fourth information from the network device during running of a first timer in the at least one timer, the second message is sent based on the fourth information, and a timer corresponding to the second message is started, the first timer being any one of the plurality of timers; if the terminal device has received the second information before the timer corresponding to the second message expires, and the second information satisfies a fourth condition, it is determined that the contention resolution succeeds when the timer corresponding to the second message expires.

40. The method of claim 39, wherein, The method further comprises: if the terminal device does not receive the second information satisfying the fourth condition before the timer corresponding to the second message expires, and all the timers corresponding to the other second messages sent by the terminal device have expired or stopped, it is determined that the contention resolution fails; or, if the terminal device does not receive the second information satisfying the fourth condition before the timer corresponding to the second message expires, and does not receive the fifth information from the network device before the timer corresponding to the second message expires, and all the timers corresponding to the other second messages sent by the terminal device have expired or stopped, it is determined that the contention resolution fails, wherein the fifth information is used to indicate retransmission of the second message.

41. The method of any one of claims 37 to 40, wherein, The method further comprises: if the terminal device does not receive the fourth information from the network device during the running of all the timers corresponding to the first messages, it is determined that the random access response reception fails.

42. The method of any one of claims 28, 30, 38, 40, wherein, The condition for the terminal device to determine that the contention resolution fails further comprises that all the timers corresponding to the first messages sent by the terminal device have expired or stopped.

43. The method of any one of claims 27-28, 32-33, 37-38, wherein, The third condition comprises that the contention resolution MAC CE is contained in the first information, and the contention resolution identifier indicated by the contention resolution MAC CE matches the CCCH SDU transmitted in the second message, or matches part of the bits in the CCCH SDU transmitted in the second message.

44. The method of any one of claims 29-30, 34-35, 39-40, wherein, The fourth condition comprises: the second information indicates reception of the PDSCH; the terminal device successfully decodes the MAC PDU carried by the PSDCH; the contention resolution MAC CE is contained in the MAC PDU, and the contention resolution identifier indicated by the contention resolution MAC CE matches the CCCH SDU transmitted in the second message, or matches part of the bits in the CCCH SDU transmitted in the second message.

45. The method of any one of claims 27-44, wherein, The first message is Msg1, and the timer is a random access response time window.

46. The method of any one of claims 27-45, wherein, The second message is Msg3, and the timer corresponding to the second message is a contention resolution timer.

47. The method of any one of claims 1 to 10, wherein, In the case of starting multiple timers, each timer corresponding to a first message, the method further comprises: if the terminal device receives the sixth information from the network device during the running of the first timer in the multiple timers, it is determined that the contention resolution succeeds, and the running timer is stopped, wherein the first timer is any one of the multiple timers; or, if the terminal device receives the sixth information from the network device during the running of the first timer in the multiple timers, and the sixth information indicates that an uplink grant for new transmission is allocated, it is determined that the contention resolution succeeds, and the running timer is stopped, wherein the first timer is any one of the multiple timers.

48. The method of claim 47, wherein, The method further comprises: if all the other timers have expired or stopped when the first timer expires, it is determined that the contention resolution fails; or, When the first timer expires, if the terminal device does not receive third information from the network device before the first timer expires, and all the other timers have expired or stopped, it is determined that the contention resolution fails, wherein the third information is used to indicate retransmission of the first message.

49. The method of any one of claims 1 to 10, wherein, In the case of starting a timer, the method further comprises: During the running of the timer, if the terminal device receives sixth information from the network device, it is determined that the contention resolution succeeds, and the timer is stopped. Or, During the running of the timer, if the terminal device receives sixth information from the network device, and the sixth information indicates that an uplink grant for new transmission is allocated, it is determined that the contention resolution succeeds, and the timer is stopped.

50. The method of claim 49, wherein, The method further comprises: If the timer expires, it is determined that the contention resolution fails. Or, When the timer expires, if the terminal device does not receive third information from the network device before the timer expires, it is determined that the contention resolution fails, wherein the third information is used to indicate retransmission of the first message.

51. The method of any one of claims 1 to 10, wherein, In the case of starting at least one timer, the method further comprises: During the running of a first timer in the at least one timer, if the terminal device receives sixth information from the network device, it is determined that the contention resolution succeeds, and the running timer is stopped, wherein the first timer is any one of the plurality of timers. Or, During the running of a first timer in the at least one timer, if the terminal device receives sixth information from the network device, and the sixth information indicates that an uplink grant for new transmission is allocated, it is determined that the contention resolution succeeds, and the running timer is stopped, wherein the first timer is any one of the plurality of timers.

52. The method of claim 51, wherein, The method further comprises: When the first timer expires, if all the other timers have expired or stopped, it is determined that the contention resolution fails. Or, When the first timer expires, if the terminal device does not receive third information from the network device before the first timer expires, and all the other timers have expired or stopped, it is determined that the contention resolution fails, wherein the third information is used to indicate retransmission of the first message.

53. The method of any one of claims 47-52, wherein, The sixth information is a physical downlink control channel (PDCCH) scrambled by a cell-radio network temporary identifier (C-RNTI).

54. The method of any one of claims 1 to 53, wherein, The plurality of first messages contain the same content.

55. The method of any one of claims 1 to 54, wherein, The number of first messages to be sent is configured by the network device, or determined by the terminal device based on a maximum number configured by the network device.

56. A wireless communication device, comprising: The apparatus comprises: a sending module configured to send a plurality of first messages; a processing module configured to start at least one timer for the plurality of first messages; the processing module is further configured to monitor downlink information from a network device during the running of the timer.

57. A terminal device, comprising: The terminal device comprises a processor and a memory, the memory stores a computer program, and the processor executes the computer program to implement the method of any one of claims 1 to 55.

58. A computer-readable storage medium, characterized in that, The storage medium stores a computer program for being executed by a processor to implement the method of any one of claims 1 to 55.

59. A chip, comprising: The chip comprises programmable logic circuitry and / or program instructions for implementing the method of any one of claims 1 to 55 when the chip is running.

60. A computer program product, characterised in that, The computer program product comprises computer instructions stored in a computer readable storage medium, and a processor reads and executes the computer instructions from the computer readable storage medium to implement the method of any one of claims 1 to 55.

Images