Wireless communication method, and related apparatus and system

Abstract

Provided in the present application are a wireless communication method, and a related apparatus and a system. The wireless communication method comprises: a first terminal sending a first message to request the execution of early data transmission (EDT); and a network device receiving the first message and then sending a second message, and the first terminal possibly receiving the second message, wherein the second message is determined on the basis of the first message and is used for indicating a result of contention resolution for the EDT that is executed by a plurality of terminals. Since a second message indicates a result of contention resolution for EDT that is executed by a plurality of terminals, the amount of occupied PDSCH resources is reduced, and the resource utilization rate is increased.

Description

Wireless communication methods and related devices and systems

[0001] This application claims priority to Chinese Patent Application No. 202411865089.8, filed on December 16, 2024, entitled "Wireless Communication Method and Related Apparatus and System", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of wireless communication technology, and in particular to a wireless communication method and related apparatus and system. Background Technology

[0003] When a non-terrestrial network (NTN) system performs the early data transmission (EDT) process, the network device and the terminal do not exchange messages 1 (Msg1) and 2 (Msg2). The terminal directly sends uplink data through message 3 (Msg3), and the network device sends message 4 (Msg4) to indicate the acknowledgment of receipt of Msg3.

[0004] However, in NTN systems, there are a large number of terminals within the coverage area of ​​network devices. If the network device sends Msg4 separately to each terminal that sends Msg3, it will consume a lot of resources and reduce resource utilization. Summary of the Invention

[0005] This application provides a wireless communication method and related apparatus and system, with the aim of reducing resource consumption and improving resource utilization.

[0006] To achieve the above objectives, this application provides the following technical solution:

[0007] Firstly, this application provides a wireless communication method, which can be executed by a terminal, or by a component configured in the terminal (such as a circuit, chip, or chip system), or by a logic module or software capable of implementing all or part of the terminal's functions. This application does not limit the scope of this method. The following description uses a terminal as an example.

[0008] The wireless communication method includes: a first terminal sending a first message, the first message being used to request the execution of Early Data Transmission (EDT); the first terminal receiving a second message, the second message being used to indicate the result of contention resolution among multiple terminals executing the EDT, the second message being determined based on the first message.

[0009] In the above technical solution, the second message is used to indicate the result of the contention resolution of multiple terminals executing EDT, thereby realizing the indication of the contention resolution result of EDT to multiple terminals through the second message, reducing resource consumption and improving resource utilization.

[0010] Optionally, there can be one or more second messages. When there are multiple second messages, the multiple second messages may occupy the same frequency domain resources but different time domain resources; or the multiple second messages may occupy different frequency domain resources but the same time domain resources; or the multiple second messages may occupy different time domain resources and different frequency domain resources.

[0011] In some possible implementations, the wireless communication method provided in this application can be applied to non-terrestrial network (NTN) systems.

[0012] In some possible implementations, the second message is a MAC layer protocol data unit (PDU), i.e., a MAC PDU.

[0013] In some possible implementations, the second message includes M MAC control units, which are used to indicate the results of contention resolution for EDT performed by the M terminals. There is a one-to-one correspondence between the M MAC control units and the results of contention resolution for EDT performed by the M terminals, where M is an integer greater than or equal to 2. This approach integrates the results of contention resolution for EDT performed by multiple terminals into the same signaling, further reducing overhead.

[0014] In some possible implementations, the M MAC control units include a first MAC control unit, which includes first information. The first information indicates a first duration, the first duration is used to determine the sending time of the third message, and the third message indicates whether the second message has been acknowledged. In this approach, the network device indicates the time point of the third message to the terminal, enabling the terminal to promptly report whether the second message has been successfully received. This facilitates rapid network decision-making for subsequent actions, such as whether retransmission is necessary, thereby improving the reliability of the second message transmission.

[0015] In some possible implementations, the first MAC control unit further includes second information indicating the resources of the third message. It should be understood that the second information may indicate the time-domain and / or frequency-domain resources of the third message.

[0016] In some possible implementations, the method further includes: the first terminal sending the third message at a first moment based on the resources of the third message, the time difference between the first moment and the second moment being a first duration, and the second moment being the moment of receiving the second message.

[0017] In some possible implementations, the second message also includes third information, which indicates the type of the M MAC control units, ensuring that the MAC control units sent by the network device can be correctly identified and processed by the terminal.

[0018] In some possible implementations, the first terminal also receives a fourth message, which indicates multiple Physical Uplink Shared Channel (PUSCH) resources; the first terminal sending the first message includes: the first terminal sending the first message based on a first PUSCH resource, wherein the first PUSCH resource belongs to multiple PUSCH resources.

[0019] In some possible implementations, the fourth message is a System Message Block (SIB) or a proprietary signaling message of the first terminal.

[0020] In some possible implementations, the first message also includes uplink data, which can reduce uplink data transmission latency and power consumption. In some implementations, the first message includes uplink data from the first terminal.

[0021] In some possible implementations, before the first terminal receives the second message, the method further includes: the first terminal receiving a fifth message, which is used to indicate the physical downlink shared channel (PDSCH) resource corresponding to the second message, and the fifth message is determined based on the first PUSCH resource; the first terminal receiving the second message includes: the first terminal receiving the second message based on the PDSCH resource indicated by the fifth message.

[0022] In some possible implementations, the first terminal receives the fifth message, including: the first terminal receives the fifth message within a first time window. It can be understood that the first time window is used to indicate the time range for sending the fifth message, and the first time window is configured.

[0023] In some possible implementations, the fifth message includes downlink control information (DCI).

[0024] In some possible implementations, the first terminal in the first message is indicated by a Temporary Mobility Identifier (S-TMIS) or an Identifier ID.

[0025] Secondly, this application provides a wireless communication method, which can be executed by a network device, or by a component (such as a circuit, chip, or chip system) configured in the network device, or by a logic module or software capable of implementing all or part of the functions of the network device. This application does not limit the scope of the method. The following description uses a network device as an example.

[0026] The wireless communication method includes: a network device receiving a first message, the first message being used to request the execution of an EDT; and the network device sending a second message, the second message being determined based on the first message.

[0027] In some possible implementations, the second message is a MAC layer protocol data unit (PDU), i.e., a MAC PDU.

[0028] In some possible implementations, the second message includes M MAC control units, which are used to indicate the result of the contention resolution of the EDT performed by the M terminals, and the M MAC control units correspond one-to-one with the result of the contention resolution of the EDT performed by the M terminals, where M is an integer greater than or equal to 2.

[0029] In some possible implementations, the M MAC control units include a first MAC control unit, which includes first information. The first information is used to indicate a first duration, the first duration is used to determine the sending time of the third message, and the third message is used to indicate whether the second message has been acknowledged.

[0030] In some possible implementations, the first MAC control unit also includes second information, which is used to indicate the resources of the third message.

[0031] In some possible implementations, the method further includes: the network device receiving the third message based on the resources of the third message, the third message being sent at a first moment, the time difference between the first moment and the second moment being a first duration, and the second moment being the moment of receiving the second message.

[0032] In some possible implementations, the second message also includes third information, which indicates the type of the M MAC control units.

[0033] In some possible implementations, before the network device receives the first message, it also includes: the network device sending a fourth message, which is used to indicate multiple physical uplink shared channel (PUSCH) resources.

[0034] In some possible implementations, the fourth message is a System Message Block (SIB) or proprietary signaling for multiple terminals, which may include the first terminal.

[0035] In some possible implementations, the first message is also used to include uplink data.

[0036] In some possible implementations, the method further includes: the network device sending a fifth message, which indicates the physical downlink shared channel (PDSCH) resource corresponding to the second message.

[0037] In some possible implementations, the fifth message includes downlink control information (DCI).

[0038] In some possible implementations, the first terminal in the first message is indicated by a Temporary Mobility Identifier (S-TMIS) or an Identifier ID.

[0039] In some possible implementations, the network device sends a fifth message based on the following rules: Rule 1 includes: the network device sends a fifth message within a first time window of multiple terminals, and multiple terminals all send a first message; Rule 2 includes: the network device performs contention conflict resolution for multiple terminals, and the number of terminals that obtain the result of contention conflict resolution does not exceed the maximum number of contention conflict resolution results that the second message can indicate for the terminals; Rule 3 includes: when the number of first messages received by the network device does not reach the maximum number of contention conflict resolution results that the second message can indicate for the terminals, the number of contention conflict resolution results indicated by the network device through the second message does not exceed the number of terminals that sent the first message.

[0040] Thirdly, this application provides a communication device including a communication module for sending a first message requesting the execution of an EDT; and for receiving a second message indicating the result of contention resolution among multiple terminals executing an EDT, the second message being determined based on the first message.

[0041] In some possible implementations, the second message is a MAC layer protocol data unit (PDU), i.e., a MAC PDU.

[0042] In some possible implementations, the second message includes M MAC control units, which are used to indicate the result of the contention resolution of the EDT performed by the M terminals, and the M MAC control units correspond one-to-one with the result of the contention resolution of the EDT performed by the M terminals, where M is an integer greater than or equal to 2.

[0043] In some possible implementations, the M MAC control units include a first MAC control unit, which includes first information. The first information is used to indicate a first duration, the first duration is used to determine the sending time of the third message, and the third message is used to indicate whether the second message has been acknowledged.

[0044] In some possible implementations, the first MAC control unit also includes second information, which is used to indicate the resources of the third message.

[0045] In some possible implementations, after receiving the second message, the communication module is also used to send the third message based on the resources of the third message at a first moment. The time difference between the first moment and the second moment is a first duration, and the second moment is the moment when the second message is received.

[0046] In some possible implementations, the second message also includes third information, which indicates the type of the M MAC control units.

[0047] In some possible implementations, before sending the first message, the communication module is also used to receive a fourth message, which indicates multiple PUSCH resources; when sending the first message, the communication module is also used to send the first message based on the first PUSCH resource, which belongs to multiple PUSCH resources.

[0048] In some possible implementations, the fourth message is a System Message Block (SIB) or a proprietary signaling message of the first terminal.

[0049] In some possible implementations, the first message is also used to include uplink data.

[0050] In some possible implementations, before receiving the second message, the communication module is also used to receive a fifth message, which is determined based on the first PUSCH resource. The fifth message is used to indicate the physical downlink shared channel (PDSCH) resource corresponding to the second message, and the first PUSCH resource is the resource occupied by the first message. When receiving the second message, the communication module is used to receive the second message based on the PDSCH resource indicated by the fifth message.

[0051] In some possible implementations, when the communication module receives the fifth message, it is used to receive the fifth message within the first time window.

[0052] Fourthly, this application provides a communication device, which includes a communication module for receiving a first message requesting the execution of an EDT; and for sending a second message determined based on the first message, which instructs the result of contention resolution for multiple terminals executing an EDT.

[0053] In some possible implementations, the second message is a MAC layer protocol data unit (PDU), i.e., a MAC PDU.

[0054] In some possible implementations, the second message includes M MAC control units, which are used to indicate the result of the contention resolution of the EDT performed by the M terminals, and the M MAC control units correspond one-to-one with the result of the contention resolution of the EDT performed by the M terminals, where M is an integer greater than or equal to 2.

[0055] In some possible implementations, the M MAC control units include a first MAC control unit, which includes first information. The first information is used to indicate a first duration, the first duration is used to determine the sending time of the third message, and the third message is used to indicate whether the second message has been acknowledged.

[0056] In some possible implementations, the first MAC control unit also includes second information, which is used to indicate the resources of the third message.

[0057] In some possible implementations, after the communication module sends the second message based on the same PDSCH resource, it is also used to receive the third message based on the resource of the third message. The third message is sent at the first moment, the time difference between the first moment and the second moment is the first duration, and the second moment is the time when the second message is received.

[0058] In some possible implementations, the second message also includes third information, which indicates the type of the M MAC control units.

[0059] In some possible implementations, the communication module is also used to send a fourth message before receiving the first message, which is used to indicate multiple PUSCH resources.

[0060] In some possible implementations, the fourth message is a System Message Block (SIB) or proprietary signaling for multiple terminals.

[0061] In some possible implementations, the first message is also used to include uplink data.

[0062] In some possible implementations, the communication module sends a fifth message before sending the second message, which indicates the PDSCH resource corresponding to the second message.

[0063] Fifthly, this application provides a communication device including a processor coupled to a memory and a communication interface, which can be used to execute instructions or data in the memory to implement the method in any possible implementation of the first aspect above.

[0064] In some possible implementations, the communication device also includes a memory.

[0065] In some possible implementations, the communication interface can be a transceiver, or an input / output interface.

[0066] In some possible implementations, the communication device is a chip configured in the terminal. When the communication device is a chip configured in the terminal, the communication interface can be an input / output interface.

[0067] In a sixth aspect, this application provides a communication device including a processor coupled to a memory and a communication interface, which can be used to execute instructions or data in the memory to implement the method in any possible implementation of the second aspect above.

[0068] In some possible implementations, the communication device also includes a memory.

[0069] In some possible implementations, the communication interface can be a transceiver, or an input / output interface.

[0070] In some possible implementations, the communication device is a chip configured in a satellite. When the communication device is a chip configured in a satellite, the communication interface can be an input / output interface.

[0071] In a seventh aspect, this application provides a processor, including: an input circuit, an output circuit, and a processing circuit. The processing circuit is used to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute the method in any possible implementation of any aspect.

[0072] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be, for example, but not limited to, output to and transmitted by a transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as both the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0073] Eighthly, this application provides a computer program product comprising: a computer program (also referred to as code or instructions) that, when run, causes a computer to perform a method in any of the possible implementations of any of the above aspects.

[0074] Ninthly, this application provides a computer-readable storage medium storing a computer program (also referred to as code or instructions) that, when run on a computer, causes the computer to perform the method in any possible implementation of any of the above aspects.

[0075] In a tenth aspect, this application provides a chip system including one or more processors for calling and executing instructions stored in memory, causing the methods in any of the above aspects or possible implementations to be executed. The chip system may be composed of chips or may include chips and other discrete devices. The chip system may include input circuitry or interfaces for transmitting information or data, and output circuitry or interfaces for receiving information or data.

[0076] In the eleventh aspect, this application provides a communication system, including the aforementioned terminal and network equipment.

[0077] In one possible implementation, the communication system may also include other devices that communicate with the terminal and / or network devices.

[0078] The technical effects of the solutions provided in the second to eleventh aspects can be found in the content of the first aspect. Attached Figure Description

[0079] Figure 1 shows an example of a network device communicating with a terminal.

[0080] Figure 2 is a schematic diagram of the network device structure;

[0081] Figure 3 is a schematic diagram of the early data transmission process based on competition;

[0082] Figure 4 is a flowchart illustrating a wireless communication method disclosed in an embodiment of this application;

[0083] Figures 5a and 5b are structural diagrams of the MAC control unit provided in the embodiments of this application;

[0084] Figure 6 is a timing diagram of the first terminal receiving the second message and sending the third message according to an embodiment of this application;

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

[0086] Figure 8 is a flowchart illustrating another wireless communication method provided in an embodiment of this application;

[0087] Figure 9 is a structural example diagram of a communication device disclosed in an embodiment of this application;

[0088] Figure 10 is a structural example diagram of another communication device disclosed in an embodiment of this application. Detailed Implementation

[0089] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. The terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be a limitation of this application. As used in the specification and appended claims of this application, the singular expressions "a," "an," "the," "the," "the," and "this" are intended to also include expressions such as "one or more," unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, "one or more" refers to one, two, or more; "and / or" describes the relationship between related objects, indicating that three relationships may exist; for example, H and / or I can represent: H alone, H and I simultaneously, and F alone, where H and I can be singular or plural. The character " / " generally indicates that the preceding and following related objects are in an "or" relationship.

[0090] References to "one implementation" or "some implementations" as used in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that implementation. Therefore, the phrases "in one implementation," "in some implementations," "in other implementations," "in yet other implementations," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0091] In this application's embodiments, "multiple" refers to two or more. Terms such as "first" and "second" are used only for descriptive distinction and should not be construed as indicating or implying relative importance or order. Similarly, messages A, B1, B2, C, and D are also used only for descriptive distinction and do not indicate the message's name, order, or importance.

[0092] The technical solution of this application can be applied to non-terrestrial network (NTN) systems such as satellite communication systems, high altitude platform station (HAPS) communication, air-to-ground (A2G) communication, and unmanned aerial vehicles (UAVs). Examples include integrated communication and navigation (ICaN) systems and global navigation satellite systems (GNSS).

[0093] Satellite communication systems can be integrated with traditional mobile communication systems. For example, mobile communication systems can be fourth-generation (4G) communication systems (e.g., Long Term Evolution (LTE) systems), worldwide interoperability for microwave access (WiMAX) communication systems, fifth-generation (5G) communication systems (e.g., new radio (NR) systems), and future mobile communication systems.

[0094] Figure 1 shows a schematic diagram of a wireless communication system provided in an embodiment of this application.

[0095] As shown in Figure 1, the wireless communication system may include: a first device 100 and a second device 200. The first device 100 is a network device, belonging to the network side for providing network communication functions. It may be an access network device or a core network device. When the first device is an access network device, the first device may be a satellite. Optionally, the satellite may have all or part of the functions of a base station. The first device may also be a satellite and a base station. The satellite may have part of the functions of a base station. The satellite and the base station cooperate to jointly provide network communication functions. The first device may also be a base station. Among them, the base station may refer to the evolved Node B (eNB or eNodeB) in LTE; or the base station in 5G network or future evolved public land mobile network (PLMN), broadband network gateway (BNG), aggregation switch or non-3rd generation partnership project (3GPP) access equipment, etc. The embodiments of this application do not specifically limit this.

[0096] Base stations can also include various forms, such as: macro base stations, micro base stations (also known as small stations), relay stations, access points, next-generation base stations (gNodeB, gNB), base band units (BBU), transmitting and receiving points (TRP), transmitting points (TP), mobile switching centers, etc. This application embodiment does not specifically limit these.

[0097] In practical applications, when network devices function as access network devices, multiple network devices can collaborate to assist terminals in achieving wireless access, with different network devices each implementing some of the functions of a base station. For example, network devices can be central units (CUs), distributed units (DUs), CU-control plane (CPs), CU-user plane (UPs), or radio units (RUs), etc. CUs and DUs can be set up separately or included in the same network element, such as a baseband unit (BBU). RUs can be included in radio equipment or radio units, such as remote radio units (RRUs), active antenna units (AAUs), or remote radio heads (RRHs).

[0098] In different systems, CU (or CU-CP and CU-UP), DU, or RU may have different names, but those skilled in the art will understand their meaning. For example, in an ORAN system, CU can also be called O-CU (Open CU), DU can also be called O-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CU-UP, and RU can also be called O-RU. Any of the units among CU (or CU-CP, CU-UP), DU, and RU in this application can be implemented through software modules, hardware modules, or a combination of software and hardware modules. CU (or CU-CP and CU-UP), DU, and RU can implement different protocol layer functions.

[0099] Figure 2 is a schematic diagram of an access network device. As an implementation example, as shown in Figure 2, the access network device may include at least one CU and at least one DU. This design can be referred to as CU and DU separation. One CU can be connected to one or more DUs. CU and DU can be separated according to the protocol layer of the wireless network: for example, the functions of the PDCP layer and above (e.g., RRC layer and SDAP layer, etc.) are set in the CU, and the functions of the protocol layers below the PDCP layer (e.g., RLC layer, media access control (MAC) layer, and PHY layer, etc.) are set in the DU; or, for another example, the functions of the protocol layers above the PDCP layer are set in the CU, and the functions of the protocol layers below the PDCP layer are set in the DU, without limitation. When the CU includes CU-CP and CU-UP, CU-CP is used to implement the control plane functions of the CU, and CU-UP is used to implement the user plane functions of the CU. For example, when the CU is configured to implement the functions of the PDCP layer, RRC layer, and SDAP layer, CU-CP is used to implement the RRC layer functions and the PDCP layer control plane functions, and CU-UP is used to implement the SDAP layer functions and the PDCP layer user plane functions. This application does not limit the names of CU and DU. The above division of CU and DU processing functions according to the protocol layer is just one example; other methods can also be used.

[0100] The CU can be connected to the core network. Optionally, the CU can have some of the functions of the core network.

[0101] Furthermore, some functions of the DU can be separated. As shown in Figure 2, this function can be implemented by a radio unit (RU). The RU can have radio frequency (RF) functionality. This application does not limit the name of the RU. The DU and RU can be split or separated at the PHY layer. For example, the DU can implement higher-level functions in the PHY layer, and the RU can implement lower-level functions in the PHY layer, or implement both lower-level functions and RF functions. Higher-level functions in the PHY layer include functions closer to the MAC layer, and lower-level functions in the PHY layer include functions closer to the RF layer. For example, higher-level functions in the PHY layer include one or more of the following: forward error correction (FEC) encoding / decoding, scrambling, or modulation / demodulation. Lower-level functions in the PHY layer include one or more of the following: fast Fourier transform (FFT) / inverse fast Fourier transform (IFFT), beamforming, or extraction and filtering of the physical random access channel (PRACH), etc. The RU can communicate with the terminal device via the air interface using RF signals. The pre-coding function of the PHY layer code can be located in the DU or the RU. The separation between the DU and RU can be done in various ways without restriction. An interface exists between the DU and RU. For example, depending on the separation method, the interface between the DU and RU can be a Common Public Radio Interface (CPRI) interface or an Enhanced Common Public Radio Interface (eCPRI) interface.

[0102] Optionally, any one of CU, CU-CP, CU-UP, DU, and RU can be a software module, a hardware structure, or a combination of software and hardware structures, without limitation. The different entities can exist in the same or different forms. For example, CU, CU-CP, CU-UP, and DU are software modules, and RU is a hardware structure. For the sake of brevity, all possible combinations are not listed here. These modules and the methods they execute are also within the protection scope of the embodiments of this application. For example, when the method of the embodiments of this application is executed by an access network device, it can be specifically executed by at least one of CU, CU-CP, CU-UP, DU, or RU.

[0103] The second device 200 can be a network access device, typically a terminal. Terminals can take various forms, such as mobile phones, tablets, computers with wireless transceiver capabilities, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminals in industrial control, vehicle-mounted terminal devices, wireless terminals in self-driving vehicles, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, wearable terminal devices, etc. Terminals are sometimes also referred to as terminal equipment, user equipment (UE), access terminal equipment, vehicle-mounted terminals, industrial control terminals, UE units, UE stations, mobile stations, mobile stations, remote stations, remote terminal equipment, mobile devices, UE terminal equipment, wireless communication equipment, UE agents, or UE devices. Terminals can also be fixed terminals or mobile terminals.

[0104] In some embodiments, the communication system may also include other devices that communicate with the first device and / or the second device, which is not a limitation of this application.

[0105] To facilitate understanding, the concepts involved in this application will be explained below.

[0106] 1. Early data transmission (EDT) refers to the process during random access where a terminal can transmit data as part of Msg3 to the network device without establishing an RRC connection. This can reduce data transmission latency and power consumption, and is particularly suitable for infrequent and small data transmission scenarios.

[0107] 2. A time slot is a concept of time division and is a basic component of the radio frame structure. A time slot can include multiple sets of time domain symbols, and each set of time domain symbols can include multiple time domain symbols.

[0108] 3. The physical uplink shared channel (PUSCH) is used to transmit uplink data.

[0109] 4. The physical downlink shared channel (PDSCH) is used to transmit downlink data.

[0110] 5. The physical downlink control channel (PDCCH) is used to transmit downlink control information.

[0111] 6. The physical uplink control channel (PUCCH) is used to transmit uplink control information.

[0112] It is understood that the above-mentioned concepts are only for the purpose of facilitating the understanding of the technical solution of this application, and do not constitute any limitation on this application.

[0113] Figure 3 shows a flowchart of early data transmission based on competition.

[0114] As shown in Figure 3, in the contention-based EDT process, the terminal and network device first execute steps 1 and 2 to synchronize timing advance (TA) and send PUSCH resource indications via Msg1 (also known as a random access preamble) and Msg2 (also known as a random access response). Then, the terminal sends Msg3 in step 3 to request EDT execution. The network device interacts with the mobility management entity (MME) of the core network in step 4 to exchange initial data. The MME and the serving gateway (S-GW) execute steps 5 to 7 to complete the transmission of uplink or downlink data. The MME can also send downlink NAS transport data to the network device in step 8a or a connection establishment indication message in step 8b. Next, the network device performs step 9 to send Msg4 (also known as RRC early data complete), and the MME, S-GW and network device perform step 10.

[0115] To save resources and improve efficiency, when the EDT process is executed in the NTN system, the network device and the terminal do not need to interact with Msg1 and Msg2. The terminal directly sends uplink data through Msg3, and the network device sends Msg4 to indicate the confirmation of receipt of Msg3.

[0116] However, in the NTN system, there are a large number of terminals within the coverage area of ​​the network device. If the network device sends Msg4 separately to each terminal requesting EDT, it will consume a lot of PDSCH resources, resulting in low resource utilization.

[0117] In view of this, embodiments of this application provide a wireless communication method. In this method, multiple terminals send Msg3 to a network device to request the execution of EDT. Based on Msg3, the network device obtains the result of contention resolution for the multiple terminals executing EDT, and then sends Msg4 to the multiple terminals. Msg4 indicates the result of contention resolution for the multiple terminals executing EDT, that is, it indicates the acknowledgment of the reception of Msg3 by the multiple terminals, thereby reducing the PDSCH channel resource occupation of Msg4 and improving resource utilization.

[0118] The solution provided in this application will be described in detail below with reference to the corresponding flowcharts. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., terminal devices, network devices) as examples of the execution subjects of this interactive illustration to illustrate the method, but this application does not limit the execution subjects of the interactive illustrations. For example, the devices (e.g., terminal devices, network devices) in the illustrative flowcharts can also be chips, chip systems, or processors that support the implementation of this method on the device, or logic modules or software that can implement all or part of the functions of the device.

[0119] Figure 4 illustrates a flowchart of a wireless communication method provided in an embodiment of this application. The flowchart uses the interaction between a first terminal and a network device as an example for illustration. The method includes the following steps:

[0120] S401, the first terminal sends the first message, and the corresponding network device receives the first message.

[0121] The first message is used to indicate a request to execute EDT.

[0122] The first message can be an RRC early data request message. For example, if the first terminal and the network device have not established an RRC connection, the first terminal sends this first message to the network device. Therefore, this first message can also be understood as a third communication message sent to the network device, i.e., Msg3.

[0123] It should be understood that multiple terminals can send messages to the network device requesting the execution of EDT. To distinguish it from the first message sent by different terminals, the first message sent by the first terminal can also be referred to as the first message of the first terminal.

[0124] In some implementations, the first message can be used to instruct the first terminal to request execution of EDT.

[0125] In some implementations, the first message can also be used to instruct multiple terminals to request EDT execution. These multiple terminals may include the first terminal and other terminals. Alternatively, the multiple terminals may exclude the first terminal and only include other terminals; that is, the first terminal acts as the sender of the first message but does not request EDT execution itself, instead requesting it on behalf of the other terminals. To implement the first message instructing terminals to request EDT execution, in some implementations, the first message may also include the terminal's identification information. Taking the first message instructing the first terminal to request EDT execution as an example, the first message includes the first terminal's identification information. The first terminal's identification information can be a network-assigned temporary mobile subscriber identity (SAE - Temporary Mobile Subscriber Identity, S-TMSI) or the first terminal's identifier (ID). Including the first terminal's identification information in the first message clearly indicates to the network device the target of the EDT request.

[0126] It should be understood that the above identifiers are merely examples and not limitations, and other methods that can distinguish terminals or identify terminal identity information can be applied to the scheme of this application.

[0127] Furthermore, the first message may also include an establishment cause for the RRC connection, which can also be referred to as a reason code. This establishment cause could be, for example, emergency access or high-priority access. In this application, since the first terminal requests EDT, the establishment cause included in the first message could be a mobile terminal initiating data transmission (mo-Data).

[0128] Optionally, the first message may also carry dedicatedInfoNAS, which is a non-access-stratum (NAS) message carried during the RRC connection establishment process, such as authentication information and encryption algorithm selection.

[0129] The first message instructs the first terminal to request execution of EDT. The first message may also include uplink data that the first terminal needs to send. This uplink data includes the first terminal's uplink service data, such as data transmission data. In some implementations, the first terminal's uplink data may be carried by dedicatedInfoNAS, meaning that dedicatedInfoNAS in the first message can include the first terminal's uplink data.

[0130] It can be understood that if the first message instructs multiple terminals to request the execution of EDT, then the first message may also include uplink data from some or all of the multiple terminals. This uplink data may be uplink service data. For example, dedicatedInfoNAS in the first message may include uplink data from multiple terminals.

[0131] It should be noted that the first terminal sends the first message based on the time-frequency domain resource of a PUSCH. In some implementations, the first terminal may randomly select a PUSCH time-frequency domain resource to send the first message, or select a PUSCH time-frequency domain resource to send the first message based on certain rules. This application does not limit this.

[0132] S402, The network device sends a second message, and the corresponding first terminal receives the second message.

[0133] The second message is determined based on the first message, and is used to indicate the result of the contention resolution of multiple terminals executing EDT.

[0134] The second message can be an RRC early data complete message. This second message can be understood as the fourth communication message between the terminal and the network device, i.e., Msg4. The second message may include a contention resolution message, which indicates the result of contention resolution for multiple terminals performing EDT.

[0135] In some implementations, the second message can be a MAC layer protocol data unit (PDU), i.e., a MAC PDU. The MAC PDU is used to indicate the result of contention resolution when multiple terminals execute EDT.

[0136] A MAC PDU may include multiple MAC control elements (MAC CEs), meaning the second message includes multiple MAC control elements, which are used to instruct multiple terminals to execute the contention resolution result of an EDT.

[0137] As shown in Figures 5a and 5b, a MAC PDU includes a MAC header and M MAC CEs, and may also include padding bytes as needed.

[0138] For example, M MAC CEs are used to indicate the result of contention resolution for multiple terminals performing EDT. It can be understood that the implementation of M MAC CEs indicating the result of contention resolution for multiple terminals performing EDT can be as follows:

[0139] In implementation method 1, as shown in Figure 5a, the second message includes M MAC CEs, which correspond to M terminals. There is a one-to-one correspondence between MAC CEs and terminals. One MAC CE is used to indicate the result of the contention resolution of EDT performed by one terminal. That is, the M MAC CEs are used to indicate the result of the contention resolution of EDT performed by M terminals, and there is a one-to-one correspondence between the M MAC CEs and the result of the contention resolution of EDT performed by M terminals. M is an integer greater than or equal to 2.

[0140] M MAC CEs share the same MAC header to form a single MAC PDU. This allows a single MAC PDU to instruct multiple terminals to resolve contention during EDT execution. Furthermore, each MAC CE corresponds one-to-one with a terminal, enabling a simpler and clearer way to instruct multiple terminals to resolve contention during EDT execution via the MAC control unit. Moreover, integrating the contention resolution results of multiple terminals' EDT executions into a single signaling message further reduces overhead.

[0141] Each MAC CE includes a Contention Resolution Identity (CRI). The CRI is a temporary identifier assigned to the terminal by the network, occupying 6 bytes. It is used to confirm the Msg3 transmission result of the terminal corresponding to that CRI. In other words, the network side confirms the terminal's access by verifying the contention resolution result of the EDT performed by the terminal corresponding to that CRI; that is, the early data transmission of the terminal corresponding to that CRI was successfully completed. Of course, 6 bytes is merely an example and does not constitute a limitation on the number of bytes occupied by the terminal's CRI.

[0142] One possible approach is that the CRI of the terminal included in the MAC CE can be the identification information of the first terminal in the first message received by the network device. That is: the network device receives a first message, which includes the identification information of the first terminal; the network device determines the access of the first terminal, and the MAC CE includes the identification information of the first terminal. For example, if the identification information of the first terminal in the first message is the S-TMSI of the first terminal, the MAC CE will include the S-TMSI of the first terminal. Another example is that if the identification information of the first terminal in the first message is the ID of the first terminal, the MAC CE will include the ID of the first terminal. In this way, the terminal can accurately identify the result of its own EDT contention resolution based on the ID, resulting in low implementation complexity.

[0143] It is understandable that if the network side does not confirm a terminal's request for EDT access, the second message sent by the network device will not include the terminal's CRI.

[0144] In this context, "the network side does not confirm the access of a terminal requesting EDT" can be understood as the network side not allowing or not allowing access to EDT through a terminal requesting EDT, or it can be understood as the network side determining not to allow access to a terminal requesting EDT.

[0145] It should be noted that after receiving the second message, the first terminal can send a third message to the network device. This third message is used to indicate whether the second message has been acknowledged by the terminal itself, that is, to indicate to the network device that the second message has been received. Therefore, the third message can also be understood as an acknowledgment message for the second message.

[0146] Based on this, in some implementations, the M MAC CEs include a first MAC CE, which may also include first information and / or second information.

[0147] The first information is used to indicate a first duration, which is used to determine the sending time of the third message. That is, after the first terminal receives the second message, it waits for the duration indicated by the first information to reach the first duration before sending the third message. For example, the first information indicates one or more time slots. Based on this, the time slot in which the first terminal receives the second message can be used as the starting time slot, and the third message can be sent in the next time slot after the one or more time slots indicated by the first information.

[0148] For example, as shown in Figure 6, the first information indicates two time slots. The first terminal receives the second message in time slot 1. The second terminal waits for two time slots based on the first information and then sends the third message in time slot 4.

[0149] As shown in Figure 5a, the first piece of information can occupy 1 byte and is the HARQ Feedback Timing Indicator. This 1-byte figure is merely an example and does not constitute a limitation on the number of bytes the first piece of information can occupy.

[0150] The second information is used to indicate the resources for the third message, that is, to instruct the first terminal to send the third message on the resources indicated by the second information after receiving the second message. The first terminal typically sends the third message on the PUCCH; therefore, the resources may include time-frequency domain resources of the PUCCH or frequency domain resources of the PUCCH. Where the second information indicates time-frequency domain resources of the PUCCH, the time-domain resources in that time-frequency domain resource can be understood as having the same duration as the first duration indicated by the first information.

[0151] As shown in Figure 5a, the second information can occupy 1 byte, which is the PUCCH Resource Indicator. This 1-byte specification is merely an example and does not constitute a limitation on the number of bytes occupied by the second information.

[0152] Therefore, in some implementations, after the first terminal receives the second message, it sends the third message at a first moment based on the resources available for the third message. The time difference between the first moment and the second moment is the first duration, where the second moment refers to the moment the second message was received. Correspondingly, when the network device receives the third message, it can determine whether the terminal has confirmed receiving the second message based on the third message.

[0153] It is understandable that, in the presence of errors, the time difference between the first moment and the second moment may not be equal to the first duration. This time difference may also be greater than or less than the first duration. In other words, the difference between the time difference between the first moment and the second moment and the first duration is the error.

[0154] It should be noted that when the first MAC CE includes the first information but not the second information, the first MAC CE only indicates the time-domain resources of the third message, but not the frequency-domain resources of the third message. The first terminal may use the frequency-domain resources of the second message as the frequency-domain resources of the third message or obtain the frequency-domain resources of the third message through other means. The first terminal sends the third message based on the frequency-domain resources of the second message and the time-domain resources indicated by the first information.

[0155] When the first MAC CE includes the second information but not the first information, the second information indicates the time-frequency domain resources of the PUCCH, and the first terminal can send the third message based on the time-frequency domain resources of the PUCCH; when the second information indicates the frequency domain resources of the PUCCH, the first terminal can determine the transmission time of the third message based on a predetermined rule, and send the third message based on the frequency domain resources of the PUCCH at the transmission time of the third message.

[0156] In one example, M MAC CEs are used in a one-to-one correspondence to indicate the result of contention resolution for EDT performed by M terminals. Each MAC CE also includes first information and / or second information; that is, all M MAC CEs are the first MAC CEs described above. The network device sends a second message including the M MAC CEs, which can be received by multiple terminals. Afterward, each terminal can locate its own MAC CE based on its own identifier and send a third message according to the first and / or second information of its own MAC CE.

[0157] The method by which each terminal sends a third message based on the first information and / or the second information can be found in the aforementioned content on the sending of the third message by the first terminal, and will not be repeated here.

[0158] In another example, M MAC CEs include a first MAC CE and a second MAC CE. The first MAC CE includes a CRI (Content Received) and includes first information and / or second information. The second MAC CE includes a CRI but does not include the first or second information. For example, M MAC CEs include X first MAC CEs and Y second MAC CEs, where X + Y = M. In other words, the M MAC CEs are divided into two parts: one part consists of MAC CEs like the first MAC CEs described above, including a CRI and including first and / or second information; the other part consists of MAC CEs including a CRI but not the first or second information. Thus, the network device sends a second message including M MAC CEs, which can be received by multiple terminals. Afterwards, a terminal, based on its own identifier, finds its own MAC CE. If the MAC CE includes the first and / or second information, the terminal can send a third message based on the first and / or second information. If a terminal finds that its own MAC CE does not include the first and / or second information, it may send a third message based on other rules, or it may not send a third message.

[0159] The first MAC CE includes first information and / or second information, enabling the network device to explicitly indicate the resources of the third message to the terminal. This allows the terminal to promptly report whether the second message has been successfully received, facilitating the network to quickly make subsequent decisions, such as whether retransmission is needed, thereby improving the reliability of the second message transmission.

[0160] In some implementations, the second message may also include third information, which indicates the type of the M MAC CEs.

[0161] It is understandable that MAC CEs include various types. For example, a MAC CE carrying a cell radio temporary identifier belongs to the type that transmits cell radio temporary identifiers. A MAC CE used to indicate the result of contention resolution during EDT (Execution Decision Processing) is also a type of MAC CE. In other words, MAC CEs can be classified into different types based on their purpose. One type is a MAC CE used to transmit cell radio temporary identifiers, and another type is a MAC CE used to indicate the result of contention resolution during EDT. To ensure that the second message sent by the network device is correctly identified and processed by the terminal, the second message can also include a field indicating the type of the M MAC CEs, i.e., third information.

[0162] In one implementation, the second message is a MAC PDU, and the MAC header in the MAC PDU includes third information. The Logical Channel Identifier (LCID) in the MAC header is used to indicate the type of MAC CE. Based on this, as shown in Figure 5a, the MAC header includes M LCIDs, and each of the M LCIDs corresponds one-to-one with one of the M MAC CEs, with each LCID indicating the type of a MAC CE.

[0163] Different types of MAC CE can be indicated by different values ​​of LCID. For example, LCID consists of one or more bits, and one or more bits of a certain value can indicate one type of MAC CE.

[0164] For example, the LCID consists of 6 bits, the value of which indicates the type of MAC CE. A value of 0 in the LCID indicates that the MAC CE carries a temporary identifier for the cell radio network; a value of 62 in the LCID indicates that the MAC CE carries the result of contention resolution of the EDT, which can be understood as including a terminal contention resolution identifier.

[0165] In another implementation, a single LCID can be used to indicate the type of multiple MAC CEs; that is, when an LCID is used to indicate the type of a MAC CE, it can indicate the type of multiple MAC CEs at once. For example, an LCID consists of one or more bits, and the values ​​of different bits can be used to indicate the type of different MAC CEs. For instance, an LCID consists of 6 bits to indicate the type of two MAC CEs; the first 3 bits indicate the type of one MAC CE, and the last 3 bits indicate the type of the other MAC CE. It should be understood that the number of bits and the meaning of the bit values ​​in this implementation are merely examples and not limitations.

[0166] In other implementations, the MAC header, in addition to indicating the type of MAC CE, can also be used to indicate the result of contention resolution for multiple terminals performing EDT. For example, the result of contention resolution for one terminal performing EDT corresponds to a mapping value, which is included in the MAC header. This mapping value can be located in the LCID or other fields of the MAC header, without limitation. As another example, the MAC header may directly include the result of contention resolution for one terminal performing EDT, which can be located in an LCID or other fields of the MAC header, without limitation.

[0167] In cases where the MAC header indicates the result of contention resolution for the EDT performed by the terminal, the MAC CE may or may not include the terminal's CRI.

[0168] In implementation method 2, M MAC CEs correspond to N terminals, where N is greater than or equal to M. That is, one MAC CE corresponds to multiple terminals, and one MAC CE can be used to indicate the result of contention resolution for multiple terminals executing EDT. Since the M MAC CEs also share the same MAC header to form a MAC PDU, this also achieves the goal of using a single MAC PDU to indicate the result of contention resolution for multiple terminals executing EDT, saving overhead.

[0169] Among the M MAC CEs, the number of race conditions resolved by the terminal executing EDT in each MAC CE may be the same or different.

[0170] Taking the result of contention resolution during EDT execution by two terminals as an example, MAC CE1 will be used to illustrate the structure of MAC CE. Referring to Figure 5b, MAC CE1 includes the CRI of terminal 1 and the CRI of terminal 2. The CRI of terminal 1 can occupy 6 bytes, and the CRI of terminal 2 can also occupy 6 bytes. Of course, 6 bytes is merely an example and does not constitute a limitation. MAC CE1 is used to confirm the Msg3 transmission results of terminals 1 and 2, that is, the network side confirms the access of terminals 1 and 2, meaning that the early data transmission of terminals 1 and 2 was successfully completed.

[0171] In some implementations, MAC CE1 may also include first information and / or second information. Detailed explanations of the first and second information can be found in the aforementioned implementations and will not be repeated here.

[0172] In some implementations, the MAC header is also used to indicate: the type of MAC CE; or, to indicate the type of MAC CE and the result of contention resolution when multiple terminals execute EDT. For details, please refer to the aforementioned implementations, which will not be repeated here.

[0173] In this embodiment of the application, the second message sent by the network device to multiple terminals is used to indicate the result of the contention resolution of the multiple terminals in performing EDT, thereby reducing the PDSCH channel resource occupation of the contention resolution message and improving resource utilization.

[0174] In some implementations, multiple terminals request to perform EDT, and the network device sends a second message based on PDSCH resources, which can be received by all the terminals that requested to perform EDT.

[0175] To improve communication reliability, network devices can send multiple second messages based on PDSCH resources. Each second message may contain the same content, all indicating the result of contention resolution for multiple terminals performing EDT (Execution Request). Alternatively, the network device can send a second message to each of the multiple terminals requesting EDT. These second messages can be based on different PDSCH resources. Different PDSCH resources can be understood as follows: multiple second messages occupy the same PDSCH time-domain resources but different PDSCH frequency-domain resources; or multiple second messages occupy different PDSCH time-domain resources but the same PDSCH frequency-domain resources; or multiple second messages occupy different PDSCH time-domain resources and different PDSCH frequency-domain resources.

[0176] It should be noted that, in addition to receiving the first message sent by the first terminal, the network device can also receive first messages sent by other terminals. For example, the network device may receive first messages sent by N terminals. Based on these N first messages, the network device obtains the second message and sends the second message to these N terminals based on the PDSCH time-frequency domain resources. N is an integer greater than or equal to 2.

[0177] The second message indicates the result of contention resolution performed by multiple terminals in EDT (Electronic Contention Resolution Technique). These multiple terminals may include N terminals, or a number less than N. Specifically, if N terminals send the first message, all or some of these N terminals can be confirmed for access by the network device. Each terminal that sent the first message can receive the second message. Therefore, a terminal can decode the received second message to determine whether it has been confirmed for access by the network side. If the decoded second message includes its own terminal contention resolution identifier, then it is determined that it has been confirmed for access by the network side.

[0178] Taking the first terminal as an example, after sending the first message in step S401, the first terminal can receive a second message sent by the network device indicating the result of contention resolution for multiple terminals performing EDT. If the first terminal decodes the second message and obtains its own contention resolution identifier (i.e., the result of contention resolution for multiple terminals performing EDT includes the result of the first terminal's contention resolution), then it determines that it has been confirmed for access by the network side. If the first terminal decodes the second message and does not obtain its own contention resolution identifier (i.e., the result of contention resolution for multiple terminals performing EDT does not include the result of the first terminal's contention resolution), then it determines that it has not been accessed by the network side.

[0179] Upon receiving the second message, the first terminal determines the outcome of its contention resolution for EDT based on the second message: the network side does not acknowledge the terminal's access, meaning the first message sent by the first terminal failed. The first terminal can then resend the first message or request EDT using the traditional method (as shown in Figure 3). If the terminal fails to send the first message several times, it can also request EDT using the traditional method (as shown in Figure 3).

[0180] It should also be noted that the network device receives the first message from N terminals, for example, N=30. Due to the carrying capacity of the second message, the second message can only support a maximum of G terminals executing the contention resolution result of EDT, where G is less than N, for example, G=10. The network device can also send multiple second messages, but the content of the multiple second messages will not be the same.

[0181] In one example, assuming the network device indicates that N terminals have been confirmed for access, the network device can also send multiple second messages, but the content of the multiple second messages is not the same. A single second message can be used to indicate the result of contention resolution for EDT performed by at most G terminals, and the indicated result of contention resolution for EDT performed by the terminals is not repeated. Multiple second messages are used together to indicate the result of contention resolution for EDT performed by N terminals. The PDSCH resources occupied by the multiple second messages are different. For example, multiple second messages may occupy the same PDSCH time domain resources but different PDSCH frequency domain resources, or multiple second messages may occupy different PDSCH time domain resources but the same PDSCH frequency domain resources, or multiple second messages may occupy different PDSCH time domain resources and also different PDSCH frequency domain resources.

[0182] In the example, N=30, G=10, and the network device sends three or more second messages based on different PDSCH resources. All the second messages sent by the network device collectively indicate the result of contention resolution for EDT performed by 30 terminals. Taking three second messages as an example, each second message indicates the result of contention resolution for EDT performed by 10 terminals. The three second messages collectively indicate the result of contention resolution for EDT performed by 30 terminals, and the result indicated by each of the three second messages is unique.

[0183] The phrase “the result of the contention resolution of the EDT executed by the terminal is not repeated” can be understood as the result of the contention resolution of the EDT executed by the second message being the result of the contention resolution of the EDT executed by different terminals. These results are not repeated between terminals, or in other words, different second messages do not repeatedly indicate the result of the contention resolution of the same terminal executing the EDT.

[0184] It should be understood that the instruction method in this application is only an example. For instance, if it is possible to instruct N terminals to execute the contention resolution result of EDT and there is still a margin, it is also possible to repeatedly instruct some terminals to execute the contention resolution result of EDT. This application is not limited in this respect.

[0185] In another example, suppose the network device indicates that Z terminals have been confirmed for access, where Z is less than N but greater than G. The network device can also send multiple second messages, but the content of these multiple second messages is not the same. A single second message can be used at most to indicate the result of contention resolution for EDT performed by G terminals, and the indicated result of contention resolution for EDT performed by the terminals is not repeated. Multiple second messages are used together to indicate the result of contention resolution for EDT performed by Z terminals. The PDSCH resources occupied by the multiple second messages are also different, such as different frequency domains, different time domains, or both.

[0186] It is understandable that: the content of multiple second messages is different, and the network device sends the second message to the corresponding terminal for the result of the contention resolution indicated by each second message.

[0187] It should also be noted that after the first terminal receives the second message, it can send uplink control information (UCI) based on PUCCH resources. Correspondingly, the network device receives the uplink control information, which is used to instruct the first terminal to confirm receipt of the second message.

[0188] The implementation of the solution in this application will be illustrated below using multiple terminals as an example.

[0189] Figure 7 illustrates a schematic flowchart of the implementation of a wireless communication method provided in an embodiment of this application. To facilitate a complete description of the solution provided in this embodiment, the following description uses the interaction between a first terminal, a second terminal, and a network device as an example, but this does not constitute a limitation.

[0190] As shown in Figure 7, the wireless communication method provided in this embodiment includes:

[0191] S701, when a network device sends message A, the first terminal receives message A, and the second terminal also receives message A.

[0192] Message A is used to indicate multiple PUSCH resources. Message A is also known as the fourth message.

[0193] In some implementations, message A can be a system information block (SIB) or part of the information in an SIB. The SIB can be SIB1, or other SIB messages such as SIB2, SIB3, SIB4, SIB5, etc., or a newly introduced SIB message.

[0194] It is understandable that network devices can broadcast SIBs, so that terminals within the coverage area of ​​the network device can receive the SIB and then learn about multiple PUSCH resources for executing EDT request messages through the SIB.

[0195] In other implementations, message A can be terminal-specific signaling, such as a Radio Resource Control (RRC) Release. Taking the first terminal as an example, after establishing an RRC connection with the network device, in some application scenarios, the network device can initiate an RRC connection release. Based on this, the network device uses RRC Release to indicate multiple PUSCH resources to the first terminal in order to execute an EDT request message. It can be understood that message A can be a portion of the terminal's proprietary signaling.

[0196] In some implementations, the multiple PUSCH resources indicated by message A may include: time-frequency domain resources of multiple PUSCHs.

[0197] It is understandable that: when a network device sends message A, and a first terminal and a second terminal receive message A, the network device can explicitly request multiple PUSCH resources for the EDT execution request message to the terminal, so that the terminal can request the execution of EDT based on a single PUSCH resource. In some implementations, the network device can use other methods to explicitly request multiple PUSCH resources for the EDT execution request message to the terminal; therefore, step S501 may not be executed.

[0198] When the first terminal and the second terminal want to perform EDT, they can perform the following steps S702 to S704.

[0199] S702, the first terminal sends message B1, and the corresponding network device receives message B1.

[0200] Message B1 is used to request the execution of EDT. For example, message B1 is used to instruct the first terminal to request the execution of EDT.

[0201] Message B1 is also referred to as the first message of the first terminal. For a detailed description of message B1, please refer to the content about the first message in step S401 of the aforementioned embodiments, which will not be repeated here.

[0202] It should be noted that after receiving message A, the first terminal can store multiple PUSCH resources indicated by message A to form a PUSCH resource pool. When the first terminal wants to execute EDT, it selects one PUSCH resource (which can be referred to as the first PUSCH resource) from the multiple PUSCH resources and sends message B1 based on the first PUSCH resource. In some implementations, the first terminal may randomly select a PUSCH resource or select a PUSCH resource based on certain rules; this application does not limit this.

[0203] S703, the second terminal sends message B2, and the corresponding network device receives message B2.

[0204] Message B2 is used to request the execution of EDT. For example, message B2 is used to instruct the second terminal to request the execution of EDT.

[0205] Message B2 may also be referred to as the first message of the second terminal. A detailed description of message B2 can be found in step S401 of the aforementioned embodiments regarding the first message, and will not be repeated here.

[0206] It should be noted that after receiving message A, the second terminal may also store the multiple PUSCH resources indicated by message A to form a PUSCH resource pool. When the second terminal wants to perform EDT, it selects one PUSCH resource (which can be referred to as the second PUSCH resource) from the multiple PUSCH resources and sends message B2 based on the second PUSCH resource. In some implementations, the second terminal may randomly select a PUSCH resource or select a PUSCH resource based on certain rules; this embodiment does not limit this.

[0207] It is understandable that, in order to avoid conflicts, the PUSCH resources used by the first terminal to send message B1 may be different from those used by the second terminal to send message B2, that is, the first PUSCH resources and the second PUSCH resources may be different.

[0208] S704, the network device sends message C, and correspondingly, both the first terminal and the second terminal receive message C based on the same PDSCH resource.

[0209] Message C is used to indicate the result of the contention resolution process of the EDT performed by the first terminal and the second terminal. Message C is also referred to as the second message. A detailed description of message C can be found in step S402 of the foregoing embodiments, and will not be repeated here.

[0210] Before sending message C, the network device can specify the PDSCH resource corresponding to message C to the terminals. The network device can specify the PDSCH resource corresponding to message C to multiple terminals by sending a single message.

[0211] To clearly illustrate the solution in this application, a specific interactive implementation example is given below.

[0212] Figure 8 shows a flowchart of another wireless communication method provided in an embodiment of this application. This embodiment is also described using the interaction between a first terminal and a second terminal and a network device as an example, but this does not constitute a limitation.

[0213] As shown in Figure 8, the wireless communication method provided in this application embodiment includes:

[0214] S801, the network device sends message A, and correspondingly, the first terminal receives message A, and the second terminal also receives message A.

[0215] Message A is used to indicate multiple PUSCH resources.

[0216] For details on the implementation of step S801, please refer to the content of step S701 above, which will not be repeated here.

[0217] S802, the first terminal sends message B1, and the corresponding network device receives message B1.

[0218] Message B1 is used to request the execution of EDT. For example, message B1 is used to instruct the first terminal to request the execution of EDT.

[0219] For details on the implementation of step S802, please refer to the content of step S702 above, which will not be repeated here.

[0220] S803, the second terminal sends message B2, and correspondingly, the network device receives message B2. For example, message B2 is used to instruct the second terminal to request the execution of EDT.

[0221] Message B2 is used to request the execution of EDT.

[0222] For details on the implementation of step S803, please refer to the content of step S703 above, which will not be repeated here.

[0223] In some implementations, after the first terminal sends message B1, a contention resolution timer (CRT) can be started; similarly, after the second terminal sends message B2, a contention resolution timer (CRT) can also be started. The contention resolution timer can also be called a contention resolution timer.

[0224] It is understandable that the timing duration of the CRT can be called the first time window, which is configured by the network device to the terminal to indicate the time limit for sending the following message D. The first time window configured by the network device for different terminals can be the same or different, that is: the first time window of the first terminal and the first time window of the second terminal can be the same or different. Figure 8 shows that the first time window of the first terminal and the first time window of the second terminal are the same.

[0225] Within the first time window, the first terminal and the second terminal can use the PDCCH message to determine whether the network device should send an indication message to indicate the PDSCH resource corresponding to message C.

[0226] S804, Network device determines the PDSCH resource corresponding to message C.

[0227] After receiving message B1 from the first terminal and message B2 from the second terminal, the network device recognizes that both the first and second terminals are executing EDT (Execution Decision Task). It needs to provide feedback on the result of the contention resolution process for the execution of EDT by the first and second terminals. Specifically, the network device sends message C to indicate the result of the contention resolution process for the execution of EDT by the first and second terminals. Message C is also referred to as the second message.

[0228] Before the network device sends message C, the network device needs to determine the PDSCH resource where message C is located (or the PDSCH resource corresponding to message C), and specify the PDSCH resource corresponding to message C to the terminal through the following step S805.

[0229] Understandable: The PDSCH resource corresponding to message C refers to the time-frequency domain resource of the PDSCH corresponding to message C.

[0230] In some implementations, the network device needs to determine the PDSCH resource corresponding to message C within the first time window of the first terminal and the second terminal, and send the PDSCH resource corresponding to message C through the following step S805. That is, the network device determines and sends the PDSCH resource corresponding to message C before the deadline of the first time window of the first terminal and the second terminal, so as to ensure that the first terminal and the second terminal can monitor the message indicating the PDSCH resource corresponding to message C within the first time window.

[0231] Limited by the amount of information that message C can carry, if the number of terminals that send the first message reaches a threshold, the network device determines the PDSCH resource corresponding to message C and sends the PDSCH resource corresponding to message C through the following step S805.

[0232] Take message C as a MAC PDU, and the maximum number of MAC CEs it includes is 10, as an example.

[0233] The network device receives the first message from the first terminal and the second terminal, and can also receive the first message sent by other terminals. When the network device receives the first message sent by 10 terminals, since the number of MAC CEs is full, the network device can request the 10 terminals to perform EDT to resolve the contention conflict, obtain the contention conflict resolution result of EDT, and determine the PDSCH resource corresponding to message C. Then, the PDSCH resource corresponding to message C is sent through the following step S705.

[0234] Assuming the network device receives fewer than 10 first messages, for example, when it receives the first message sent by 8 terminals, but the first time window of one or more of the 8 terminals is about to reach its deadline, the network device can also perform EDT on the 8 terminals to resolve contention conflicts, obtain the result of the contention conflict resolution of EDT, and determine the PDSCH resource corresponding to message C. Then, the PDSCH resource corresponding to message C is sent through the following step S705.

[0235] Therefore, we can conclude that:

[0236] The PDSCH resources corresponding to message C sent by the network device shall not exceed the first time window of the terminal that sent the first message.

[0237] The number of terminals that obtain the result of contention resolution when the network device performs contention resolution for multiple terminals does not exceed the maximum number of contention resolution results that message C can indicate to the terminals. Of course, if the number of times the network device receives the first message does not reach the maximum number of contention resolution results that message C can indicate to the terminals, the number of contention resolution results indicated by the network device through message C does not exceed the number of terminals that sent the first message.

[0238] In the aforementioned scenario, where a network device sends multiple messages C with identical content, all indicative of the outcome of contention resolution for multiple terminals performing EDT (Execution Time-Frequency Tolerance). The network device can determine the PDSCH time-frequency domain resources corresponding to each message C. These multiple messages C may have the same time-domain resources but different frequency-domain resources, or the same frequency-domain resources but different time-domain resources, or both different time-domain and frequency-domain resources. The network device further sends multiple messages D based on step S805, each message D indicating the time-frequency domain resources corresponding to one message C.

[0239] The requirements and rules for network devices to determine and send the time-frequency domain resources corresponding to each message C are described above and will not be repeated here.

[0240] As mentioned above: the network device receives a total of N first messages (including messages B1 to BN) sent by terminals. Limited by the carrying capacity of the second message (i.e., message C), the second message can support a maximum of G terminals executing the contention resolution result of EDT, where G is less than N. The network device sends multiple second messages with different contents. The network device can determine the PDSCH time-frequency domain resources corresponding to each message C. Multiple messages C may have the same time-domain resources but different frequency-domain resources, or the same frequency-domain resources but different time-domain resources, or both different time-domain and frequency-domain resources. The network device also sends multiple messages D based on the following step S805, each message D indicating the time-frequency domain resources corresponding to one message C.

[0241] If one or more terminals among N terminals are about to reach the end of their first time window, the network device will prioritize confirming their access, determine the PDSCH resource corresponding to message C, and send message D through the following step S805 before the first time window expires. In other words, the network device prioritizes determining the PDSCH resource corresponding to message C for terminals whose first time window is about to expire, and sends message D through the following step S805 before the first time window expires to indicate the result of contention resolution for EDT performed by such terminals.

[0242] S805, the network device sends message D, and correspondingly, the first terminal receives message D, and the second terminal also receives message D.

[0243] Message D is used to indicate the PDSCH resource corresponding to message C. Message D may also be referred to as the fifth message.

[0244] In some implementations, message D can be downlink control information (DCI). This means that message D can occupy some or all of the fields in the DCI. The DCI can be DCI 1_0 or DCI1_1.

[0245] The radio network temporary identifier (RNTI) for scrambling DCI can be calculated based on the PUSCH resource selected by the terminal. Therefore, the scrambling RNTI of message D sent by the network device will be different depending on the PUSCH resource selected by different terminals.

[0246] In the example of the first terminal and the second terminal, the network device sends message D1 to the first terminal. Message D1 is a DCI, which can indicate the PDSCH resource corresponding to message C. It is scrambled using the RNTI calculated by the PUSCH resource selected by the first terminal. The network device sends message D2 to the second terminal. Message D2 is a DCI, which can also indicate the PDSCH resource corresponding to message C. It is scrambled using the RNTI calculated by the PUSCH resource selected by the second terminal.

[0247] The first terminal receives message D1 and decodes and verifies message D1 based on the RNTI calculated using its selected PUSCH resources to confirm that message D1 was sent by the network device. If the first terminal can correctly decode and verify message D1, it means that message D1 was sent by the network device to the first terminal. The first terminal can then normally utilize the PDSCH resources corresponding to message C indicated by message D1.

[0248] Similarly, when the second terminal receives message D2, it also decodes and verifies message D2 based on the RNTI calculated by itself using the PUSCH resource it selected. If the second terminal can correctly decode and verify message D2, it means that message D2 is a message sent to the second terminal by the network device, and the second terminal can normally use the PDSCH resource corresponding to message C indicated by message D2.

[0249] The specific implementation of calculating RNTI based on the PUSCH resources selected by the terminal can be found in relevant technologies, and will not be elaborated here.

[0250] In other implementations, the network device sends message D based on the PDCCH, and can send different messages D based on different PDCCH resources. Based on this, the first terminal listens for messages on the PDCCH within the first time window to receive message D; similarly, the second terminal also listens for messages on the PDCCH within the first time window to receive message D.

[0251] It should be noted that, taking the first terminal as an example, the network device sends message D only after the first terminal's first time window has elapsed. That is, if the first terminal does not receive message D within the first time window, it can resend message B1 at the end of the first time window, or request EDT using the traditional method (as shown in Figure 3). If the first terminal receives message D before the end of the first time window, it can also stop the CRT timing.

[0252] It should also be noted that in the example of the first terminal and the second terminal, the PDSCH resource corresponding to the message C indicated by the message D sent by the network device to the first terminal and the second terminal is the same PDSCH resource, that is, the time domain resource of the PDSCH is the same, and the frequency domain resource of the PDSCH is also the same.

[0253] For example, message D is a DCI, which includes resource block (RB) allocation information, namely frequency domain resource allocation information and time domain resource allocation information. In the DCI sent by the network device to the first terminal and the DCI sent to the second terminal, the frequency domain resource allocation information is the same frequency domain resource of the PDSCH, and the time domain resource allocation information is the same time domain resource of the PDSCH.

[0254] S806, the network device sends message C, and correspondingly, both the first terminal and the second terminal receive message C based on the same PDSCH resource.

[0255] Message C is used to indicate the result of the contention resolution of the EDT between the first terminal and the second terminal.

[0256] For details on the implementation of step S806, please refer to the content of step S704 above, which will not be repeated here.

[0257] After executing step S806, the network device can further execute subsequent downlink data or signaling transmission based on the contention resolution result of the EDT performed by the first and second terminals as indicated by message D. It can be understood that if message D indicates that the result of the EDT contention resolution performed by a terminal is: the network device confirms the terminal's access, and the network device can send downlink data or signaling to the terminal according to service requirements. Step S807 below is illustrated using the example of the network device confirming the access of the second terminal.

[0258] S807: The network device sends downlink data or signaling, and the corresponding second terminal receives downlink data or signaling.

[0259] Downlink data can be understood as downlink service data sent by network devices, such as data transmission data. Signaling can be understood as downlink control signaling sent by network devices, such as signaling for configuration and measurement.

[0260] In one application scenario, the second terminal sends uplink data for a service through step S803. After the network device confirms the access of the second terminal through step S806, it can also send downlink data for the service to the second terminal based on step S807.

[0261] Figure 9 is a schematic block diagram of a communication device provided in an embodiment of this application. As shown in Figure 9, the communication device 900 may include a communication module 920. The communication module 920 can implement corresponding communication functions, which can be internal communication functions of the communication device 900 or communication functions between the communication device 900 and other devices. Optionally, the communication module 920 may also be referred to as a communication interface or a transceiver module.

[0262] Optionally, the communication device 900 further includes a processing module 910. The processing module 910 can perform corresponding processing functions.

[0263] Optionally, the communication device 900 further includes a storage module, which can be used to store instructions and / or data; the processing module 910 can read the instructions and / or data in the storage module so that the communication device 900 can implement the aforementioned method embodiments.

[0264] In one possible design, the communication device 900 may correspond to the terminal device in the above method embodiments, such as a first terminal, a second terminal, or a component (such as a circuit, chip, or chip system) configured in the terminal device. The communication device 900 can be used to execute the steps or processes performed by the terminal device in any of the above method embodiments.

[0265] For example, the communication module 920 is used to send a first message to request the execution of EDT, and also to receive a second message to indicate the result of the contention resolution of multiple terminals executing EDT, the second message being determined based on the first message.

[0266] For example, the communication module 920 is also used to send a third message, which indicates whether the second message has been acknowledged as received.

[0267] For example, the communication module 920 is also used to receive a fourth message, which is used to indicate multiple PUSCH resources.

[0268] For example, the communication module 920 is also used to receive a fifth message, which indicates the PDSCH resource corresponding to the second message.

[0269] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0270] In one possible design, the communication device 900 may correspond to the network device in the above method embodiments, or to a component (such as a circuit, chip, or chip system) configured in the network device. The communication device 900 can be used to perform the steps or processes performed by the network device in any of the above method embodiments.

[0271] For example, the communication module 920 is used to receive a first message, which requests the execution of EDT, and is also used to send a second message, which is determined based on the first message, and is used to indicate the result of the contention resolution of multiple terminals executing EDT.

[0272] For example, the communication module 920 is also used to send a fourth message, which indicates multiple PUSCH resources.

[0273] For example, the communication module 920 is also used to send a fifth message, which indicates the PDSCH resource corresponding to the second message.

[0274] The above are merely examples; for detailed steps or procedures, please refer to the descriptions in the foregoing embodiments.

[0275] Figure 10 is another schematic block diagram of a communication device 1000 provided in an embodiment of this application. The communication device 1000 may be a terminal device, a network device, a chip, chip system, or processor that implements the above methods. The communication device 1000 can be used to implement the methods described in the above method embodiments; for details, please refer to the descriptions in the above method embodiments.

[0276] As shown in Figure 10, the communication device 1000 may include one or more processors 1010, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 1010 can be a general-purpose processor or a dedicated processor, such as a baseband processor or a central processing unit. The baseband processor can be used to process communication protocols and communication data, while the central processing unit can be used to control the communication device 1000 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

[0277] In an alternative design, the processor 1010 may also store instructions and / or data, which can be executed by the processor 1010 to cause the communication device 1000 to perform the methods described in the above method embodiments.

[0278] In another alternative design, the communication device 1000 may include a communication interface 1020 for implementing receiving and transmitting functions. For example, the communication interface 1020 may be a transceiver circuit, interface, interface circuit, or transceiver. The transceiver circuit, interface, interface circuit, or transceiver for implementing receiving and transmitting functions may be separate or integrated. The aforementioned transceiver circuit, interface, interface circuit, or transceiver may be used for reading and writing code / data, or it may be used for transmitting or relaying signals.

[0279] Optionally, the communication device 1000 may include one or more memories 1030, which may store instructions that can be executed on the processor 1010, causing the communication device 1000 to perform the methods described in the above method embodiments. Optionally, the memories 1030 may also store data. Optionally, the processor 1010 may also store instructions and / or data. The processor 1010 and the memories 1030 may be provided separately or integrated together.

[0280] It should be understood that, in one possible design, the steps in the method embodiments provided in this application can be implemented by integrated logic circuits in the processor's hardware or by instructions in software form. The steps of the methods disclosed in the embodiments of this application can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules in the processor. The software modules can reside in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method. To avoid repetition, detailed descriptions are not provided here.

[0281] In one implementation, the communication device 1000 may correspond to the terminal device in the above method embodiments and may be used to execute the various steps and / or processes executed by the terminal device (such as a first terminal or a second terminal) in the above method embodiments. The processor 1010 may be used to execute instructions stored in the memory 1030, and when the processor 1010 executes the instructions stored in the memory, the processor 1010 is used to execute the various steps and / or processes of the above method embodiments corresponding to the terminal device.

[0282] In another implementation, the communication device 1000 may correspond to the network device in the above method embodiments and may be used to execute the various steps and / or processes executed by the network device in the above method embodiments. The processor 1010 may be used to execute instructions stored in the memory 1030, and when the processor 1010 executes the instructions stored in the memory, the processor 1010 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0283] It is understood that the aforementioned processor can be one or more chips. For example, the processor can be a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), a system-on-chip (SoC), a central processing unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD), or other integrated chips.

[0284] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous linked dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0285] This application also provides a computer-readable storage medium storing instructions that, when executed on one or more computing devices, cause the one or more computing devices to perform the wireless communication method described in the above embodiments.

[0286] Computer-readable storage media can be non-transitory computer-readable storage media, such as read-only memory (ROM), random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage devices.

[0287] This application also provides a computer program product. When executed by one or more computing devices, the computer program product enables the computing devices to execute any of the aforementioned wireless communication methods. The computer program product can be a software installation package. When any of the aforementioned wireless communication methods needs to be used, the computer program product can be downloaded and executed on a computer.

[0288] This application also provides a processor, including: an input circuit, an output circuit, and a processing circuit. The processing circuit receives signals through the input circuit and transmits signals through the output circuit, causing the processor to execute the wireless communication method described in the above embodiments.

[0289] In specific implementation, the processor can be one or more chips, the input circuit can be input pins, the output circuit can be output pins, and the processing circuit can be transistors, gate circuits, flip-flops, and various logic circuits. The input signal received by the input circuit can be received and input by, for example, but not limited to, a receiver, and the signal output by the output circuit can be output to, for example, but not limited to, a transmitter and transmitted by the transmitter. Furthermore, the input circuit and the output circuit can be the same circuit, which is used as the input circuit and the output circuit at different times. This application does not limit the specific implementation of the processor and various circuits.

[0290] This application also provides a chip system including one or more processors for calling and executing instructions stored in a memory, thereby causing the wireless communication method described in the above embodiments to be executed. The chip system may be composed of a chip or may include chips and other discrete devices. The chip system may include input circuitry or interfaces for transmitting information or data, and output circuitry or interfaces for receiving information or data.

[0291] In the embodiments of this application, the terms and English abbreviations are exemplary examples given for ease of description and should not be construed as limiting the application in any way. This application does not preclude the possibility of defining other terms that can achieve the same or similar functions in existing or future agreements.

[0292] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented in software, it can be implemented, in whole or in part, as a computer program product. The computer program product includes one or more computer instructions. When these computer instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated.

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

[0294] It should be understood that in the various embodiments of this application, the sequence number of each process does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0295] In summary, the above description is merely a preferred embodiment of the technical solution of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of protection of this application.

Claims

1. A method of wireless communication, the method comprising: include: The first terminal sends a first message, which is used to request the execution of Early Data Transmission (EDT). The first terminal receives a second message, which is used to indicate the result of the contention resolution of multiple terminals performing EDT, and the second message is determined based on the first message.

2. The method of claim 1, wherein, The second message includes M Media Access Control (MAC) units, which are used to indicate the result of contention resolution for EDT performed by the M terminals. The M MAC units correspond one-to-one with the result of contention resolution for EDT performed by the M terminals, and M is an integer greater than or equal to 2.

3. The method of claim 2, wherein, The M MAC control units include a first MAC control unit, which includes first information. The first information is used to indicate a first duration, and the first duration is used to determine the sending time of the third message. The third message is used to indicate whether the second message has been acknowledged as received.

4. The method of claim 3, wherein, The first MAC control unit also includes second information, which is used to indicate the resources of the third message.

5. The method of claim 4, wherein, The method further includes: The first terminal sends the third message at a first moment based on the resources of the third message. The time difference between the first moment and the second moment is the first duration, and the second moment is the time when the second message is received.

6. The method according to any one of claims 1 to 5, characterized in that, The second message also includes third information, which indicates the type of the M MAC control units.

7. The method according to any one of claims 1 to 6, characterized in that, The method further includes: The first terminal receives a fourth message, which is used to indicate multiple Physical Uplink Shared Channel (PUSCH) resources; Sending the first message by the first terminal includes: the first terminal sending the first message based on a first PUSCH resource, wherein the first PUSCH resource belongs to the plurality of PUSCH resources.

8. The method of claim 7, wherein, The fourth message is a System Message Block (SIB) or a proprietary signaling message of the first terminal.

9. The method according to any one of claims 1 to 8, characterized in that, The first message also includes uplink data.

10. The method according to claim 7 or 8, characterized in that, The method further includes: The first terminal receives a fifth message, which is used to indicate the PDSCH resource corresponding to the second message. The fifth message is determined based on the first PUSCH resource. The first terminal receiving the second message includes: the first terminal receiving the second message based on the PDSCH resources indicated by the fifth message.

11. The method of claim 10, wherein, The first terminal receives the fifth message, which includes: The first terminal receives the fifth message within a first time window, where the first time window is configured.

12. A method of wireless communication, the method comprising: include: Receive a first message, which is used to request the execution of Early Data Transmission (EDT); A second message is sent, which is determined based on the first message, and the second message is used to instruct the multiple terminals on the result of the contention resolution of the EDT.

13. The method of claim 12, wherein, The second message includes M MAC control units, which are used to indicate the result of the contention resolution of the EDT performed by the M terminals, and the M MAC control units correspond one-to-one with the result of the contention resolution of the EDT performed by the M terminals, where M is an integer greater than or equal to 2.

14. The method of claim 13, wherein, The M MAC control units include a first MAC control unit, which includes first information. The first information is used to indicate a first duration, and the first duration is used to determine the sending time of the third message. The third message is used to indicate whether the second message has been acknowledged as received.

15. The method of claim 14, wherein, The first MAC control unit also includes second information, which is used to indicate the resources of the third message.

16. The method of claim 15, wherein, The method further includes: The third message is received based on the resources of the third message. The third message is sent at a first moment, the time difference between the first moment and the second moment is the first duration, and the second moment is the time when the second message is received.

17. The method of any one of claims 13 to 16, wherein, The second message also includes third information, which indicates the type of the M MAC control units.

18. The method of any one of claims 12 to 17, wherein, The method further includes: A fourth message is sent, which is used to indicate multiple physical uplink shared channel (PUSCH) resources.

19. The method of claim 18, wherein, The fourth message is a System Message Block (SIB) or a proprietary signaling message from the multiple terminals.

20. The method of any one of claims 12 to 19, wherein, The first message also includes uplink data.

21. The method of any one of claims 12 to 20, wherein, The method further includes: The fifth message is determined based on the first PUSCH resource. The fifth message is used to indicate the physical downlink shared channel (PDSCH) resource corresponding to the second message. The first PUSCH resource is the resource occupied by the first message. Send the fifth message.

22. A communications device, characterized by Includes a communication module, the communication device being used to perform the method as described in any one of claims 1 to 11, or the method as described in any one of claims 12 to 21.

23. A communications device, characterized by include: Memory is used to store computer programs or computer instructions; A processor for executing a computer program or computer instructions stored in the memory, causing the communication device to perform the method as described in any one of claims 1 to 11, or the method as described in any one of claims 12 to 21.

24. A computer storage medium for storing a computer program, which, when executed, performs the method of any one of claims 1 to 11, or the method of any one of claims 12 to 21.

25. A computer program product, characterised in that, It stores instructions that, when the computer program product is run on the electronic device, cause the electronic device to perform the method as described in any one of claims 1 to 11, or the method as described in any one of claims 12 to 21.

26. A wireless communication system, characterized by The device includes a first terminal and a network device, wherein the first terminal is configured to perform the method as described in any one of claims 1 to 11; and the network device is configured to perform the method as described in any one of claims 12 to 21.

27. A chip system, characterized by It includes one or more processors for calling and executing instructions stored in memory, such that the method of any one of claims 1 to 11 is performed, or the method of any one of claims 12 to 21 is performed.

Images