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: a terminal device sends a plurality of first messages (610); on the basis of the plurality of first messages, the terminal device starts or restarts a first timer (620); and during the running of the first timer, the terminal device monitors downlink information from a network device (630). A terminal device sends a first message, restarts or starts a first timer, and adjusts the mode in which the terminal device detects downlink information from a network device, so that the terminal device monitors a response from the network device as much as possible during the running of the first timer, thereby reducing the possibility of missing the response to the first message from the network device.

Description

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

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

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

[0003] In the case of multiple terminal devices transmitting at the same time, collision problems between terminal devices are prone to occur. Therefore, the field of communication technology has begun to introduce DSA (Diversity Slotted ALOHA) and CRDSA (Contention Resolution Diversity Slotted ALOHA) to reduce the probability of collision and further improve the capacity of uplink by using multiple copies of the same data transmission.

[0004] However, after the introduction of DSA and CRDSA, how terminal devices listen to the response of the network device still needs further discussion and research.

[0005] SUMMARY

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

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

[0008] sending a plurality of first messages;

[0009] starting or restarting a first timer based on the plurality of first messages;

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

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

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

[0013] a processing module configured to start or restart a first timer based on the plurality of first messages, and monitor downlink information from a network device during the running of the first timer.

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

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

[0016] According to an aspect of the embodiments of the present application, a chip is provided, which 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 wireless communication method.

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

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

[0019] The terminal device adjusts the detection manner of the terminal device to the downlink information from the network device by sending the first message, restarting or starting the first timer, so that the terminal device can monitor the response of the network device as much as possible during the running of the first timer, and the possibility of missing the response of the network device to the first message is reduced. BRIEF DESCRIPTION OF DRAWINGS

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

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

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

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

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

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

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

[0027] FIG. 8 is a structural schematic diagram of a terminal device according to an embodiment of the present application. DETAILED DESCRIPTION

[0028] For the purpose, technical solutions and advantages of the present application to be more clear, 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 for more clearly illustrating 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. It can be known by those skilled in the art that, with the evolution of network architecture and the emergence 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, the conventional communication system supports a limited number of connections, which is easy to implement. However, with the development of communication technology, the mobile communication system will not only support the 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. The 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, and 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, and can also be applied to a Terrestrial Networks (TN) system. Generally, the NTN adopts a satellite communication mode to provide communication services to ground users. The NTN system currently includes an NR-NTN and an IoT-NTN system, and other NTN systems can be included in the future.

[0035] Please refer to FIG. 1, which shows a schematic diagram of a network architecture 100 provided by 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 (such as the B5G (Beyond 5G, Super Fifth 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, frequency domain resource, or 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-speed 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 explained. The following related technologies can be combined with the technical solutions of the embodiments of the present application as optional solutions, 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] I. LTE random access process

[0044] In LTE, the random access process 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 process: 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 the RRC_CONNECTED state, DL (DownLink) data arrives, and UL is out of sync at this time;

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

[0050] 6. SR failed;

[0051] 7. Synchronous reconfiguration request from RRC.

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

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

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

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

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

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

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

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

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

[0061] In the NR system, RA-RNTI is calculated 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 of the first OFDM (Orthogonal Frequency Division Multiplexing) symbol of the PRACH timing (0≤s_id≤14), t_id is the index of the first slot of the PRACH timing in the system frame (0≤t_id≤80), f_id is the index of the PRACH timing in the frequency domain (0≤f_id≤8), and ul_carrier_id is the UL carrier used for random access preamble transmission (0 represents NUL (Normal Uplink) carrier, and 1 represents SUL (Supplementary Uplink) carrier).

[0064] For eMTC (enhanced Machine-Type Communication) UEs, RA-RNTI is calculated 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 of the corresponding PRACH in that subframe (0≤f_id<6), and PRACH resources are numbered sequentially in the frequency domain from low to high. SFN_id is the index of the first SFN (System Frame Number) of PRACH transmission, and Wmax is the maximum RAR window length supported by eMTC, which is 400 subframes.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0088] Step 0: Leader assignment (Msg0)

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

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

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

[0092] For explanations of Msg1 and Msg2, please refer to the above text; they 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 achieve uplink synchronization with the cell. During the random access process, the network device can know the time when the terminal device sends the random access preamble based on the RACH time-frequency resources used by the random access preamble received from the terminal device. Therefore, the network device determines the initial TA (Timing Advance) of the terminal device based on the transmission and reception times of the random access preamble, and informs the terminal device through the RAR.

[0094] II. EDT (Early Data Transmission)

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

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

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

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

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

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

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

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

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

[0104] III. PUR (Preconfigured Uplink Resources)

[0105] To further reduce signaling overhead and terminal power consumption on top of EDT, the PUR feature was introduced for NB-IoT and eMTC. This feature allows the base station to configure PUR resources for the UE while releasing it to RRC IDLE state. The UE can then use these PUR resources for uplink transmission in RRC IDLE state without initiating a random access procedure. When configuring the PUR for the UE, the network can also simultaneously configure a DMRS (DeModulation Reference Signal) cyclic shift, allowing up to two UEs to share the same PUSCH (Physical Uplink Shared Channel) resource (distinguished by the DMRS). By skipping the random access procedure, uplink transmission efficiency can be further improved, and terminal device power consumption can be further reduced.

[0106] Before performing a PUR transmission, the UE needs to verify the validity of the TA. The validity of the TA is determined based on one or more of the following conditions:

[0107] a) Has the service area changed?

[0108] b) Has the TAT (Timing Advance Timer) timed out?

[0109] c) Changes in UE RSRP (Reference Signal Receiving Power).

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

[0111] In traditional EDT, the base station allocates PUSCH resources for the initial transmission of Msg3 to the UE via Msg2. In traditional PUR, the base station provides PUR configuration information to the UE via an RRC connection release message when releasing the UE to the RRC IDLE state. Regarding the PUSCH resources used for Msg3 transmission in RACH-less EDT, RAN2#126 has reached the following conclusion: RAN2 focuses 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 resource allocation).

[0112] Based on the above conclusions, in RACH-less EDT, if multiple UEs select the same PUSCH resource to transmit Msg3 (i.e., multiple UEs experience Msg3 conflict), the base station can only successfully receive Msg3 from one UE at most. However, in most cases, the base station cannot correctly receive Msg3 from all these conflicting UEs. Thus, UEs that fail to resolve contention need to retry Msg3 transmission. Similarly, for CBRA (contention-based Random Access), for UEs that select the same RO (RACH Occasion) and the same preamble to send Msg1, the success of contention resolution can only be determined after Msg4 is received. UEs that fail to resolve contention need to retry Msg1. Msg3 conflicts in RACH-less EDT and Msg1 conflicts in CBRA waste system PUSCH and PRACH resources and increase the latency for UE data transmission or access, thus affecting user experience.

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

[0114] The introduction of DSA and CRDSA technologies in RACH-less EDT aims to reduce the probability of Msg3 collisions, thereby further improving UL capacity. This technology can also be used in random access procedures. The introduction of DSA and CRDSA in RACH-less EDT and random access affects the behavior of terminal devices listening for network device responses. Therefore, it is necessary to regulate the behavior of terminal devices at the standards level to ensure that responses sent by network devices are not missed.

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

[0116] Step 610: The terminal device sends multiple first messages.

[0117] In some embodiments, the terminal device sends multiple first messages to the network device. The first message can be any message sent by the terminal device to the network device. The first message is sent in multiple copies.

[0118] In some embodiments, the first message is a message in a RACH-less EDT, namely Msg3. In some embodiments, the first message is a copy of Msg3 sent by the terminal device in a RACH-less EDT. In some embodiments, the first message carries uplink data. RACH-less EDT is an EDT mechanism that transmits Msg3 directly without going through a random access procedure; uplink data is transmitted via Msg3 in a RACH-less EDT.

[0119] In some embodiments, the transmission resources used to transmit multiple first messages are configured by the network device. In some embodiments, the network device may broadcast the pre-configuration information of the RACH-less EDT to multiple terminal devices to configure the transmission resources used to transmit multiple first messages. In some embodiments, the network device may also configure the transmission resources used to transmit multiple first messages for the terminal devices via an RRC configuration message, wherein the RRC configuration message carries the pre-configuration information of the RACH-less EDT.

[0120] In some embodiments, before the terminal device sends multiple first messages, the terminal device receives pre-configuration information for a RACH-less EDT sent by the network device. This pre-configuration information includes Msg3 / PUSCH resource configuration information. The Msg3 / PUSCH resource configuration information is used to indicate the transmission resources of the PUSCH used to carry the first messages. The transmission resources are pre-configured uplink resources (PUR), including time-domain resources and frequency-domain resources. The pre-configuration information for the RACH-less EDT may also include at least one of the following: terminal device identification information, timing advance, and power control parameters, etc. The terminal device identification information is a unique identifier assigned to the terminal device by the network device, such as an RNTI (Radio Network Temporary Identifier).

[0121] In some embodiments, the Msg3 / PUSCH resource configuration information indicates multiple resource groups configured by the network device. Each resource group includes transmission resources for at least one PUSCH. In some embodiments, the first message is transmitted on any one of the PUSCHs in the resource group.

[0122] In some embodiments, the terminal device selects a target resource group from multiple resource groups, each resource group containing multiple transmission opportunities. The terminal device randomly selects N transmission opportunities from the multiple transmission opportunities contained in the target resource group to send the first message, where N is an integer greater than 1.

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

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

[0125] Transmission timing refers to the time-frequency resources used by the terminal device when sending the first message on the uplink channel. Understandably, the selected N transmission timings correspond to different time-domain resources and / or frequency-domain resources. The uplink channel can be a PUSCH.

[0126] In some embodiments, the same first message is repeatedly transmitted multiple times during any one of the selected N transmission opportunities. The multiple first messages sent by the terminal device are considered as first messages sent at different transmission opportunities; repeated transmission refers to transmitting copies of the same first message multiple times during a specified transmission opportunity. In some embodiments, whether the terminal device repeatedly transmits the first message depends on the configuration of the network device.

[0127] In some embodiments, the first message includes third information, which indicates the transmission timing of each of the multiple first messages. In some embodiments, the third information may include identification information of the transmission timing of each of the multiple first messages. Optionally, when the network device determines the multiple transmission timings included in the resource group, it assigns identification information to each of the multiple transmission timings. In some embodiments, the third information may be range information of the transmission timings, which indicates transmission timings within a specified range in the resource group.

[0128] In some embodiments, any two first messages among a plurality of first messages may contain the same or different content. In some embodiments, when any two first messages among a plurality of first messages contain different content, any number of first messages among the plurality of first messages are associated with each other. For example, when the amount of uplink data that the terminal device needs to transmit is large, a segmented transmission method is used to transmit a portion of the uplink data using multiple first messages respectively. Therefore, after receiving multiple first messages, the network device can reassemble the uplink data according to the third information contained in the first messages.

[0129] In the above method, by carrying third information in the first message, the network device can determine other first messages associated with the first message based on the third information after receiving the first message.

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

[0131] In some embodiments, where the number of first messages is configured by the network device, the network device can configure the number of first messages to be sent by the terminal device through an RRC configuration message or broadcast.

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

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

[0134] Step 620: The terminal device starts or restarts the first timer based on multiple first messages.

[0135] The first timer is used to confirm the contention resolution status within a specified time interval, which refers to the runtime of the first timer. In some embodiments, the first timer is a MAC Contention Resolution Timer. A MAC contention resolution timer is a timer used to manage and control the contention resolution process. Understandably, the first timer is started when the terminal device sends the first of a plurality of first messages; it is restarted when the first timer times out or is interrupted by other events. In some embodiments, the terminal device maintains at most one first timer.

[0136] In this application, the success / failure of contention resolution can also be referred to as the success / failure of conflict resolution.

[0137] In some embodiments, the way the first timer is started or restarted in a RACH-less EDT differs depending on the random access protocol, and this will be explained in detail below.

[0138] (I) DSA-based RACH-less EDT

[0139] In the DSA-based RACH-less EDT mechanism, N first messages are sent at N randomly selected transmission times from the target resource group. Here, N is less than or equal to Nmax.

[0140] In some embodiments, when the RACH-less EDT is a DSA-based RACH-less EDT, the contents of multiple first messages may be the same or different. The contents of the first message refer to the payload of the first message. The payload refers to the effective data portion actually carried in the first message, that is, the uplink data that the first message needs to carry.

[0141] When multiple first messages contain identical content, transmitting N first messages with the same content at N randomly selected transmission points can improve the success rate and reliability of uplink data transmission. Even if the aforementioned N first messages fail due to collisions or interference, the uplink data transmission is considered successful as long as at least one first message is successfully transmitted.

[0142] When multiple first messages contain different content, these multiple first messages can carry a portion of the uplink data to be transmitted. This method enables data fragmentation and reassembly, thereby enabling the transmission of larger amounts of uplink data.

[0143] In some embodiments, a first timer is started or restarted based on each first message. Since the terminal device can only maintain a maximum of one first timer, sending each first message starts or restarts the first timer once.

[0144] In some embodiments, the timing of starting or restarting the first timer can be one of the following two scenarios:

[0145] (1) The terminal device starts or restarts the first timer when it completes sending a first message. That is, the terminal device starts or restarts the first timer when it completes sending a first message.

[0146] (2) After each first message is sent, the terminal device starts or restarts a first timer for a first interval duration. The first interval duration is determined based on the round-trip time delay between the terminal device and the network device. The first interval duration can be equal to the round-trip time delay, that is, the duration for which the terminal device starts or restarts the first timer is the first interval duration after the first message is sent. Of course, the first interval duration can also be a duration different from the round-trip time delay, such as a duration slightly longer than the round-trip time delay. The round-trip time (RTT) between the terminal device and the network device refers to the time required from when the terminal device sends a signal to the network device to when it receives a return signal from the network device. In some embodiments, timing advance can be used to estimate the round-trip time delay between the terminal device and the network device, or PING (Packet Internet Groper) test can be used to obtain the round-trip time delay between the terminal device and the network device. This application does not limit this.

[0147] In the above method, for DSA-based RACH-less EDT, since the network device only relies on the transmission of a single Msg3 copy (first message) to receive Msg3, it is only necessary to start or restart the first timer after the transmission of a single Msg3 copy. This ensures that the terminal device has the opportunity to receive the response from the network device after each Msg3 copy transmission.

[0148] (II) RACH-less EDT based on CRDSA

[0149] In the CRDSA-based RACH-less EDT mechanism, N first messages are also sent at N randomly selected transmission times within the target resource group. However, unlike CRDSA-based RACH-less EDT, the first timer is only started once. Compared to DSA-based RACH-less EDT, in CRDSA-based RACH-less EDT, network devices can use Joint Interference Cancellation (JIC) technology to receive the first message sent by the terminal device, thus resolving the collision and interference issues of the first message.

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

[0151] In some embodiments, when the RACH-less EDT is a CRDSA-based RACH-less EDT, multiple first messages contain identical content. Since the network device decodes any received first message after successfully receiving it, interference from other conflicting first messages can be eliminated based on the content of the received first message. For example, if first message 1 is successfully decoded in transmission time 1, the network device can use the content of first message 1 to eliminate interference from first message 2 in transmission time 2. Here, first message 2 may be a first message sent by another terminal device. Therefore, when the RACH-less EDT is a CRDSA-based RACH-less EDT, multiple first messages sent by the same terminal device should contain identical content.

[0152] In some embodiments, the terminal device starts a first timer based on a target first message among a plurality of first messages, where the target first message is the first message sent. That is, the timing of starting the first timer is determined based on the moment when the terminal device sends the first message among a plurality of first messages.

[0153] In some embodiments, the timing of starting or restarting the first timer can be one of the following two scenarios:

[0154] (1) When the terminal device completes the transmission of the first target message, it starts the first timer. That is to say, the terminal device starts the first timer when it completes the transmission of the first message of the above multiple first messages.

[0155] (2) After the terminal device completes the transmission of the first target message, a first timer is started after a first interval. The first interval is determined based on the round-trip time delay between the terminal device and the network device. That is, the first timer is started after the first interval of the first message of the above multiple first messages is completed.

[0156] During the process of RACH-less EDT sending the aforementioned multiple first messages to CRDSA-based RACH-less EDT, the first timer only needs to be started once. However, during the process of RACH-less EDT sending the aforementioned multiple first messages to CRDSA-based RACH-less EDT, the number of times the first timer is started or restarted is determined by the number of multiple first messages.

[0157] In some embodiments, the duration of the first timer is related to at least one of the following: the timing of the transmission of the target first message, the resource group used to transmit the first message, and the last transmission timing in the resource group used to transmit the first message.

[0158] The duration of the first timer is at least sufficient to allow the terminal device to complete the transmission of the aforementioned multiple first messages during the execution of the first timer. For example, the duration of the first timer can be the delay between the transmission timing of the target first message and the transmission timing of the last first message. Alternatively, the duration of the first timer can be the delay between the transmission timing of the target first message and the last transmission timing in the resource group used to transmit the first message. Or, the duration of the first timer can be the delay between the first transmission timing in the resource group used to transmit the first message and the last transmission timing in the resource group used to transmit the first message. All of the above examples satisfy the requirement of allowing the terminal device to complete the transmission of the aforementioned multiple first messages.

[0159] In some embodiments, the duration of the first timer is determined based on the configured duration of the first timer and the first duration, which is related to at least one of the following: the timing of the transmission of the target first message, the resource group used to transmit the first message, and the last transmission timing in the resource group used to transmit the first message.

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

[0161] The first duration is a duration determined based on the first message to be sent by the terminal device. The first duration ensures that the terminal device completes the transmission of the aforementioned multiple first messages during the execution of the first timer. In some embodiments, the duration of the first timer is determined by adding the configured duration of the first timer to the first duration. For example, the first duration plus the configured duration of the first timer is the delay between the transmission timing of the target first message and the transmission timing of the last sent first message. For example, the first duration plus the configured duration of the first timer is the delay between the transmission timing of the target first message and the last transmission timing in the resource group used to transmit the first message. For example, the first duration plus the configured duration of the first timer is the delay between the first transmission timing in the resource group used to transmit the first message and the last transmission timing in the resource group used to transmit the first message.

[0162] In some embodiments, the duration of the first timer is such that the network device's response to the last sent first message is received. In some embodiments, the configured duration of the first timer is greater than or equal to the sum of the latency between the network device and the terminal device, and the processing latency of the network device for the last sent first message.

[0163] In the above method, based on CRDSA-based RACH-less EDT, since network devices may use all Msg3 copies (first messages) in the selected Msg3 resource group (from different terminal devices) to receive Msg3, the terminal device waiting for the network device's response needs to take into account the last available transmission opportunity in the selected Msg3 resource group. Therefore, the duration of the first timer needs to take into account the processing latency of this part of the network device to ensure that the network device's response is not missed.

[0164] In some embodiments, the starting or restarting of the first timer by the terminal device is determined by the configuration of the network device.

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

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

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

[0168] In some embodiments, when the configuration information indicates that joint interference cancellation technology is not used to receive the first message, the terminal device starts or restarts the first timer based on each first message. That is, when the network device does not use joint interference cancellation technology to receive the first message, the terminal device adopts the method of starting or restarting the first timer corresponding to DSA-based RACH-less EDT.

[0169] In some embodiments, the configuration information directly instructs the terminal device to use the method of starting or restarting the first timer corresponding to the DSA-based RACH-less EDT. Correspondingly, the network device does not use joint interference cancellation technology to receive the first message.

[0170] In some embodiments, when the configuration information indicates that joint interference cancellation technology is used to receive the first message, the terminal device starts a first timer based on a target first message among multiple first messages, where the target first message is the first message sent. That is, when the network device uses joint interference cancellation technology to receive the first message, the method of starting or restarting the first timer corresponding to CRDSA-based RACH-less EDT is adopted.

[0171] In some embodiments, the configuration information directly instructs the terminal device to start or restart the first timer using the CRDSA-based RACH-less EDT. Correspondingly, the network device uses joint interference cancellation technology to receive the first message.

[0172] Step 630: During the operation of the first timer, the terminal device monitors downlink information from the network device.

[0173] After being started or restarted, the first timer runs continuously for a specified time period. This specified time period indicates the runtime of the first timer. If no event occurs that would interrupt the first timer after it is started or restarted, the first timer will continue running until the runtime equals the duration of the first timer.

[0174] In some embodiments, during the operation of the first timer, the terminal device monitors a first downlink channel scrambled with a first sequence; wherein the first sequence is associated with the terminal device, or the first sequence is associated with the transmission resources of the first message.

[0175] Scrambling is a technique used to enhance signal immunity to interference and data confidentiality. When a network device transmits downlink information on a first downlink channel with a first scrambled sequence, it needs to scramble the downlink information using the first sequence. In some embodiments, the downlink information is XORed bit by bit based on the first sequence to obtain the scrambled downlink information. Understandably, only a terminal device possessing the first sequence can successfully descramble the scrambled downlink information.

[0176] In some embodiments, the first sequence is the first RNTI.

[0177] In some embodiments, when a first sequence is associated with a terminal device, the network device assigns a first RNTI to each terminal device. The first sequence for each terminal device is then unique, used to uniquely descramble the scrambled downlink information sent by the network device. That is, only the terminal device possessing the first sequence can correctly decode the scrambled downlink information and restore the correct downlink information.

[0178] In some embodiments, where the first sequence is associated with the transmission resources of the first message, the first sequence includes at least one second sequence. In some embodiments, the second sequence is configured by a network device. In some embodiments, the second sequence is a second RNTI. The transmission resources include time-domain resources and / or frequency-domain resources.

[0179] In some embodiments, for the Mth first message sent, the first sequence includes M second sequences, where M is an integer greater than 0 and less than or equal to N. After the first timer is started or restarted for the Mth time, the first sequence includes the M second sequences associated with the previous M first message transmissions. That is, each first message transmission is associated with a second sequence, therefore, the first sequence corresponding to each first message includes one or more second sequences. For example, after the first timer is started or restarted for the second time, the first sequence includes 2 second sequences. For example, after the first timer is started or restarted for the third time, the first sequence includes 3 second sequences.

[0180] In some embodiments, the first downlink channel is the PDCCH.

[0181] In some embodiments, the scheme provided in this application can also be applied to the random access process, and is similar to that applied to RACH-less EDT. Therefore, for details on how the scheme provided in this application is applied to the random access process, please refer to the corresponding content on the application to RACH-less EDT, which will not be repeated here.

[0182] The solution provided in this application embodiment involves a terminal device sending a first message to restart or start a first timer, thereby adjusting the terminal device's detection method for downlink information from a network device. This enables the terminal device to monitor the network device's response as much as possible during the operation of the first timer, reducing the possibility of missing the network device's response to the first message.

[0183] In some embodiments, the determination of whether contention resolution is successful may vary depending on the different random access protocols. The following embodiments will classify and illustrate this.

[0184] Scenario 1: RACH-less EDT based on DSA, determining the success / failure of race condition resolution (method 1)

[0185] In some embodiments, during the operation of the first timer, if the terminal device receives first information from the network device, and the first information satisfies a first condition, it is determined that the contention has been successfully resolved.

[0186] The first message is a response from the network device to a first message sent by the terminal device. In some embodiments, the first message may be a response to the most recently sent first message by the network device. In some embodiments, the first message may be a response to a previously sent first message.

[0187] In some embodiments, the first condition includes:

[0188] Condition 1: The first information indicates that the PDSCH should be received;

[0189] Condition 2: The terminal device successfully decodes the Medium Access Control Protocol Data Unit (MAC PDU) carried by the PSDCH;

[0190] Condition 3: The MAC PDU contains a collision resolution Medium Access Control Control Elements (MAC CE), and the collision resolution identifier indicated by the collision resolution MAC CE matches the Common Control Channel Service Data Unit (CCCH SDU) transmitted in the first message, or matches a portion of the bits in the CCCH SDU transmitted in the first message.

[0191] In some embodiments, for condition 1 in the first condition, the first information is descrambled based on the first sequence to obtain descrambled first information. In some embodiments, the first information is XORed bit by bit based on the first sequence to obtain descrambled first information. The descrambled first information instructs the terminal device to receive the PDSCH. Receiving the PDSCH means that the terminal device receives downlink data sent by the network device on the PDSCH indicated by the descrambled first information.

[0192] In some embodiments, the descrambled first information is used to indicate a second downlink channel. The network device uses the second downlink channel to transmit first downlink data. In some embodiments, the second downlink channel is a PDSCH. In some embodiments, the terminal device receives the first downlink data transmitted by the network device on the second downlink channel based on the descrambled first information. The first downlink data includes a MAC PDU carried by the PDSCH. A MAC PDU is a basic unit for transmitting data, including data and / or control information.

[0193] In some embodiments, for condition 2, the terminal device decodes the MAC PDU carried by the PDSCH to obtain the decoded MAC PDU.

[0194] The Conflict Resolution MAC CE is a control element used to resolve conflicts when multiple terminal devices simultaneously attempt to access network resources, and it is used to verify the identity of the terminal devices. The Conflict Resolution MAC CE includes the identification information of the terminal devices, such as the terminal device's C-RNTI (Cell Radio Network Temporary Identifier) ​​and the temporary identifier used by the terminal device in the RACH-less EDT.

[0195] The Conflict Resolution Identity is used to identify the terminal device to which the first message received by the network device belongs. In some embodiments, the Conflict Resolution Identity includes identification information of at least one terminal device.

[0196] In some embodiments, the first information includes a CCCH SDU. A CCCH SDU refers to a Service Data Unit transmitted via the Common Control Channel and is included in an RRC message, such as an RRC connection request, RRC connection reconfiguration, RRC connection release, and RRC connection request. In some embodiments, the CCCH SDU includes identification information of the terminal device. Therefore, the identification information of the terminal device may occupy all bits or only a portion of the bits in the CCCH SDU.

[0197] Therefore, if the identification information of at least one terminal device included in the conflict resolution identifier matches the identification information of the terminal device included in the CCCH SDU, then the conflict resolution identifier is determined to match the CCCH SDU transmitted in the first message, or to match a portion of the bits in the CCCH SDU transmitted in the first message. For example, the first k bits of a CCCH SDU including j bits are the identification information of the terminal device, where j is an integer greater than 0, and k is an integer greater than 0 and less than j. Here, k is a predefined value.

[0198] In scenario 1, the terminal device needs to receive the first information from the network device during the operation of the first timer, and the received first information must simultaneously satisfy three of the first conditions in order to determine that the contention has been successfully resolved.

[0199] In some embodiments, if the contention is successfully resolved, the terminal device will not start or restart the first timer. This is because the terminal device will send the next first message at the next transmission opportunity, and after the contention is resolved, the first timer will not be started or restarted due to sending the first message, nor will it be started due to the PDCCH scheduling of the first message retransmission.

[0200] In some embodiments, if the first timer is not started or restarted due to subsequent transmission of the first message after the first timer expires, it is determined that the race resolution has failed.

[0201] In case 1, if the terminal device does not receive the first information that satisfies the first condition before the first timer expires in the last startup, then the race condition resolution is determined to have failed.

[0202] Scenario 2: RACH-less EDT based on DSA, determining the success / failure of race condition resolution (method 2)

[0203] In some embodiments, when the first timer expires, if the terminal device has received the first information before the first timer expires, and the first information satisfies the first condition, it is determined that the contention resolution was successful.

[0204] In some embodiments, subsequent steps following the receipt of the first information can be performed after the first timer expires. For example, subsequent steps may include at least one of the following: descrambling the first information, receiving the PDSCH based on the first information, and decoding the MAC PDU carried by the PDSCH. It is understood that as long as the first information is received before the first timer expires, and the first information is confirmed to meet the first condition after the first timer expires, the contention can be considered successfully resolved.

[0205] In scenario 2, the terminal device receives the first information from the network device before the first timer expires, but only after the first timer expires does it complete the judgment on whether the first information meets the first condition. If the first information meets the first condition, the contention is determined to be resolved successfully.

[0206] In some embodiments, if it is determined that the contention has been successfully resolved, the terminal device will not start or restart the first timer.

[0207] In case 2, the determination of whether the race resolution has failed is similar to case 1. If the terminal device has not received the first information that satisfies the first condition before the first timer expires in the last startup, then the race resolution is determined to have failed.

[0208] Scenario 3: RACH-less EDT based on CRDSA, determining the success / failure of race condition resolution (method 1)

[0209] In case 3, the determination of whether the contention resolution was successful is similar to case 1. During the operation of the first timer, if the terminal device receives the first information from the network device, and the first information meets the first condition, the contention resolution is determined to be successful.

[0210] In scenario 3, the failure to resolve the competition may be due to the following two reasons:

[0211] 1) If the terminal device does not receive the first information before the first timer expires, or if the terminal device has received the first information before the first timer expires but the first information does not meet the first condition, then the race resolution is determined to have failed.

[0212] If the terminal device does not receive any first message before the first timer expires, it indicates that the network device did not respond to any first message sent by the terminal device during the first timer's operation, thus confirming that the contention issue between the terminal devices has not been resolved.

[0213] The competition can only be resolved if the first message satisfies all three conditions in the first condition. If the first message does not satisfy any one of the three conditions in the first condition, the competition is determined to have failed.

[0214] 2) When the first timer expires, if the terminal device has not received the first information before the first timer expires, or if the terminal device has received the first information before the first timer expires but the first information does not meet the first condition, and has not received the second information from the network device before the first timer expires, then the contention resolution is determined to have failed. The second information is used to indicate the retransmission of the first message.

[0215] In some embodiments, if the network device fails to decode the first message, the network device sends a second message to the terminal device, requesting the terminal device to retransmit the first message.

[0216] Scenario 4: RACH-less EDT based on CRDSA, determining the success / failure of race condition resolution (method 2)

[0217] In scenario 4, similar to scenario 2, the terminal device receives the first information from the network device before the first timer expires, but only after the first timer expires does it complete the judgment on whether the first information meets the first condition. If the first information meets the first condition, the contention is determined to be resolved successfully.

[0218] In scenario 4, similar to scenario 3, the failure to resolve the contention is determined to include two situations: 1. If the terminal device does not receive the first message from the network device before the first timer expires, or if it receives the first message from the network device but the first message does not meet the first condition, then the contention resolution is determined to have failed; 2. If the terminal device does not receive the first message from the network device before the first timer expires, or does not receive the second message requesting the terminal device to retransmit the first message, then the contention resolution is determined to have failed.

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

[0220] Please refer to Figure 7, which shows a block diagram of a wireless communication device according to an embodiment of this application. This device has the function of implementing the above-described wireless communication method; the function can be implemented in hardware or by hardware executing corresponding software. As shown in Figure 7, the device 700 may include a transmitting module 710 and a processing module 720.

[0221] The sending module 710 is used to send multiple first messages.

[0222] The processing module 720 is used to start or restart a first timer based on the plurality of first messages; and to monitor downlink information from network devices during the operation of the first timer.

[0223] In some embodiments, the processing module 720 is configured to start or restart the first timer based on each first message.

[0224] In some embodiments, the processing module 720 is configured to start or restart the first timer when each first message is sent; or, at a first interval after each first message is sent, start or restart the first timer, the first interval being determined based on the round-trip delay between the terminal device and the network device.

[0225] In some embodiments, the processing module 720 is configured to start the first timer based on a target first message among the plurality of first messages, wherein the target first message is the first message sent.

[0226] In some embodiments, the processing module 720 is configured to start the first timer when the target first message is sent; or, to start the first timer after a first interval after the target first message is sent, wherein the first interval is determined based on the round-trip delay between the terminal device and the network device.

[0227] In some embodiments, the duration of the first timer is related to at least one of the following: the timing of the transmission of the target first message, the resource group used to transmit the first message, and the last transmission timing in the resource group used to transmit the first message.

[0228] In some embodiments, the duration of the first timer is determined based on the configured duration of the first timer and a first duration, the first duration being related to at least one of the following: the transmission timing of the target first message, the resource group used to transmit the first message, and the last transmission timing in the resource group used to transmit the first message.

[0229] In some embodiments, the processing module 720 is configured to monitor a first downlink channel scrambled with a first sequence during the operation of the first timer; wherein the first sequence is associated with the terminal device, or the first sequence is associated with the transmission resources of the first message.

[0230] In some embodiments, the processing module 720 is further configured to, during the operation of the first timer, if the terminal device receives first information from the network device, determine that the contention has been successfully resolved if the first information satisfies a first condition.

[0231] In some embodiments, the processing module 720 is further configured to stop the running first timer if it is determined that the contention has been successfully resolved.

[0232] In some embodiments, the processing module 720 is further configured to, when the first timer expires, if the terminal device has received the first information before the first timer expires, determine that the contention has been successfully resolved if the first information satisfies the first condition.

[0233] In some embodiments, the processing module 720 is further configured to not start or restart the first timer if it is determined that the contention has been successfully resolved.

[0234] In some embodiments, the processing module 720 is further configured to, when the first timer expires, determine that the contention resolution has failed if the terminal device did not receive the first information before the first timer expires, or if the terminal device received the first information before the first timer expires but the first information does not meet the first condition; or, when the first timer expires, determine that the contention resolution has failed if the terminal device did not receive the first information before the first timer expires, or if the terminal device received the first information before the first timer expires but the first information does not meet the first condition, and no second information from the network device was received before the first timer expires, wherein the second information is used to indicate retransmission of the first message.

[0235] In some embodiments, the conditions under which the terminal device determines that the contention resolution has failed further include: the first timer is not subsequently started or restarted due to the first message transmission.

[0236] In some embodiments, the first condition includes: the first information indicates reception of PDSCH; the terminal device successfully decodes the MAC PDU carried by the PDSCH; the MAC PDU contains a MAC CE, and the conflict resolution identifier indicated by the conflict resolution MAC CE matches the CCCH SDU transmitted in the first message, or matches a portion of the bits in the CCCH SDU transmitted in the first message.

[0237] In some embodiments, the first message is a message in a RACH-less EDT.

[0238] In some embodiments, when the RACH-less EDT is a DSA-based RACH-less EDT, the contents of the plurality of first messages may be the same or different; or, when the RACH-less EDT is a CRDSA-based RACH-less EDT, the contents of the plurality of first messages may be the same.

[0239] In some embodiments, the first message includes third information, which is used to indicate the transmission timing of each of the plurality of first messages.

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

[0241] In some embodiments, the processing module 720 is further configured to select a target resource group from a plurality of resource groups, each resource group containing a plurality of transmission opportunities; and randomly select N transmission opportunities from the plurality of transmission opportunities contained in the target resource group to send the first message, where N is an integer greater than 1.

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

[0243] In some embodiments, the device 700 further includes a receiving module (not shown in FIG7).

[0244] A receiving module is used to receive configuration information, which indicates whether to use joint interference cancellation technology to receive the first message.

[0245] In some embodiments, when the configuration information indicates that the joint interference cancellation technology is not used to receive the first message, the terminal device starts or restarts the first timer based on each first message; when the configuration information indicates that the joint interference cancellation technology is used to receive the first message, the terminal device starts the first timer based on a target first message among the plurality of first messages, wherein the target first message is the first message sent.

[0246] It should be noted that the above embodiments only illustrate the division of the above functional modules when implementing the device. In actual applications, the above functions can be assigned to different functional modules according to actual needs, that is, the content structure of the device can be divided into different functional modules to complete all or part of the functions described above.

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

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

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

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

[0251] The memory 803 can be connected to the processor 801 and the transceiver 802.

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

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

[0254] In some embodiments, the transceiver 802 is configured to send a plurality of first messages. The processor 801 is configured to start or restart a first timer based on the plurality of first messages; and during the operation of the first timer, monitor downlink information from network devices.

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

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

[0257] In some embodiments, the computer-readable storage medium may include ROM (Read-Only Memory), RAM (Random-Access Memory), SSD (Solid State Drives), or optical disc, etc. The random access memory may include ReRAM (Resistance Random Access Memory) and DRAM (Dynamic Random Access Memory).

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

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

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

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

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

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

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

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

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

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

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

Claims

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

2. The method of claim 1, wherein, The starting or restarting of the first timer based on the plurality of first messages comprises: starting or restarting the first timer based on each first message.

3. The method of claim 2, wherein, The starting or restarting of the first timer based on each first message comprises: starting or restarting the first timer upon completion of each first message sending; or starting or restarting the first timer after a first interval of time from completion of each first message sending, the first interval of time being determined based on a round trip time between the terminal device and the network device.

4. The method of claim 1, wherein, The starting or restarting of the first timer based on the plurality of first messages comprises: starting the first timer based on a target first message in the plurality of first messages, the target first message being a first sent first message.

5. The method of claim 4, wherein, The starting of the first timer based on the first sent first message in the plurality of first messages comprises: starting the first timer upon completion of sending the target first message; or starting the first timer after a first interval of time from completion of sending the target first message, the first interval of time being determined based on a round trip time between the terminal device and the network device.

6. The method according to claim 4 or 5, characterized in that, A duration of the first timer is related to at least one of: a transmission occasion of the target first message, a resource group used for transmitting the first message, and a last transmission occasion in the resource group used for transmitting the first message.

7. The method according to any one of claims 4 to 6, characterized in that, The duration of the first timer is determined according to a configured duration of the first timer and a first duration, the first duration being related to at least one of: a transmission occasion of the target first message, a resource group used for transmitting the first message, and a last transmission occasion in the resource group used for transmitting the first message.

8. The method according to any one of claims 1 to 7, characterized in that, The monitoring of the downlink information from the network device during running of the first timer comprises: monitoring a first downlink channel scrambled by a first sequence during running of the first timer; wherein the first sequence is associated with the terminal device, or the first sequence is associated with transmission resources of the first message.

9. The method of claim 1, wherein, The method further comprises: if the terminal device receives first information from the network device during running of the first timer, determining that contention resolution is successful if the first information satisfies a first condition.

10. The method of claim 9, wherein, The method further comprises: stopping the first timer that is running if it is determined that contention resolution is successful.

11. The method of claim 1, wherein, The method further comprises: if the terminal device has received first information before the first timer expires, determining that contention resolution is successful if the first information satisfies a first condition when the first timer expires.

12. The method according to any one of claims 9 to 11, characterized in that, The method further comprises: not starting or restarting the first timer if it is determined that contention resolution is successful.

13. The method according to any one of claims 9 to 12, characterized in that, The method further comprises: determining that contention resolution fails when the first timer expires, if the terminal device does not receive the first information before the first timer expires, or the terminal device receives the first information before the first timer expires, but the first information does not satisfy the first condition; or, determining that contention resolution fails when the first timer expires, if the terminal device does not receive the first information before the first timer expires, or the terminal device receives the first information before the first timer expires, but the first information does not satisfy the first condition, and the terminal device does not receive second information from the network device before the first timer expires, wherein the second information is used to indicate retransmitting the first message.

14. The method of claim 13, wherein, The condition that the terminal device determines that contention resolution fails further comprises that no first timer is started or restarted due to the first message transmission subsequently.

15. The method according to any one of claims 9 to 14, characterized in that, The first condition comprises: The first information indicates receiving a physical downlink shared channel (PDSCH); The terminal device successfully decodes a medium access control layer protocol data unit (MAC PDU) carried by the PDSCH; The MAC PDU contains a collision resolution medium access control layer control element (MAC CE), and the collision resolution MAC CE indicates a collision resolution identifier 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.

16. The method according to any one of claims 1 to 15, characterized in that, The first message is a message in RACH-less EDT.

17. The method of claim 16, wherein, in a case that the RACH-less EDT is a DSA-based RACH-less EDT, the contents contained in the plurality of first messages are the same or different; or, in a case that the RACH-less EDT is a CRDSA-based RACH-less EDT, the contents contained in the plurality of first messages are the same.

18. The method according to any one of claims 1 to 17, characterized in that, The first message contains third information, and the third information is used to indicate transmission occasions of the plurality of first messages respectively.

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

20. The method according to any one of claims 1 to 19, characterized in that, The method further comprises: selecting a target resource group from a plurality of resource groups, each resource group containing a plurality of transmission occasions; randomly selecting N transmission occasions from the plurality of transmission occasions contained in the target resource group for sending the first message, N being an integer greater than 1.

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

22. The method according to any one of claims 1 to 21, characterized in that, The method further comprises: receiving configuration information, the configuration information being used to indicate whether to receive the first message using joint interference cancellation technology.

23. The method of claim 22, wherein, In a case where the configuration information indicates not to receive the first messages using the joint interference cancellation technique, the terminal device starts or restarts the first timer based on each first message; In a case where the configuration information indicates to receive the first messages using the joint interference cancellation technique, the terminal device starts the first timer based on a target first message in the multiple first messages, the target first message being a first transmitted first message.

24. A wireless communication device, comprising: The apparatus comprises: a sending module, configured to send multiple first messages; a processing module, configured to start or restart a first timer based on the multiple first messages, and monitor downlink information from a network device during running of the first timer.

25. A terminal device, comprising: The terminal device comprises a processor and a memory, the memory storing a computer program, and the processor executes the computer program to implement the method in any of claims 1 to 23.

26. A computer-readable storage medium, characterized in that, The storage medium stores a computer program, and the computer program is used by a processor to implement the method in any of claims 1 to 23.

27. A chip, characterized by The chip comprises programmable logic circuit and / or program instructions, and when the chip is running, the programmable logic circuit and / or program instructions are used to implement the method in any of claims 1 to 23.

28. 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 in any of claims 1 to 23.

Images