Wireless communication method, terminal device, and network device

Abstract

Provided are a wireless communication method, a terminal device, and a network device. The method comprises: a terminal device receives a first message sent by a network device, wherein the first message comprises information used for indicating that the terminal device has successfully transmitted first data, and the first message satisfies one or more of the following conditions: the first message carries timing advance (TA) information of the terminal device; and the information used for indicating that the terminal device has successfully transmitted first data corresponds to a first medium access control (MAC) control element (CE). Compared to an RRC message encapsulation mode, the MAC CE no longer requires upper-layer encapsulation. Therefore, in the present application, compared to transmitting the first message by means of an RRC message in the conventional solution, using the information which is included in the first message, corresponds to the first MAC CE and is used for indicating that the terminal device has successfully transmitted first data helps to reduce the air interface overhead for transmitting the first message.

Description

Wireless communication method, terminal equipment and network equipment Technical Field

[0001] The present application relates to the field of communication technology, and more specifically, to a wireless communication method, terminal equipment, and network equipment. Background Art

[0002] In some scenarios, the network device sends a first message to the terminal device to indicate that the terminal device has successfully transmitted the first data. The first message is a radio resource control (RRC) message, and the air interface overhead required to transmit the RRC message is relatively large.

[0003] Summary of the Invention

[0004] The present application provides a wireless communication method, terminal device, and network device. The following introduces various aspects of the present application.

[0005] In a first aspect, a method for wireless communication is provided, including: a terminal device receiving a first message sent by a network device, the first message including information for indicating that the terminal device has successfully transmitted first data, wherein the first message satisfies one or more of the following: the first message carries timing advance (TA) information of the terminal device; the information for indicating that the terminal device has successfully transmitted the first data corresponds to a first medium access control (MAC) control element (CE).

[0006] According to a second aspect, a method for wireless communication is provided, including: a network device sends a first message to a terminal device, the first message including information for indicating that the terminal device has successfully transmitted first data, wherein the first message satisfies one or more of the following: the first message carries timing advance (TA) information of the terminal device; the information for indicating that the terminal device has successfully transmitted the first data corresponds to a first media access control MAC control element CE.

[0007] According to a third aspect, a terminal device is provided, comprising: a receiving unit for receiving a first message sent by a network device, the first message comprising information for indicating that the terminal device has successfully transmitted the first data, wherein the first message satisfies one or more of the following conditions: the first message carries the timing advance TA information of the terminal device; the information for indicating that the terminal device has successfully transmitted the first data corresponds to a first media access control MAC control element CE.

[0008] In a fourth aspect, a network device is provided, including: a sending unit, used to send a first message to a terminal device, the first message including information for indicating that the terminal device has successfully transmitted the first data, wherein the first message satisfies one or more of the following: the first message carries the timing advance TA information of the terminal device; the information for indicating that the terminal device has successfully transmitted the first data corresponds to a first media access control MAC control element CE.

[0009] In a fifth aspect, a terminal device is provided, comprising a processor, a memory, and a communication interface, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the terminal device executes part or all of the steps in the method of the first aspect.

[0010] In a sixth aspect, a network device is provided, comprising a processor, a memory, and a transceiver, wherein the memory is used to store one or more computer programs, and the processor is used to call the computer program in the memory so that the network device executes part or all of the steps in the method of the second aspect.

[0011] In a seventh aspect, an embodiment of the present application provides a communication system, which includes the above-mentioned terminal device and / or network device. In another possible design, the system may also include other devices that interact with the terminal device or network device in the solution provided in the embodiment of the present application.

[0012] In an eighth aspect, an embodiment of the present application provides a computer-readable storage medium, which stores a computer program, and the computer program enables a communication device (for example, a terminal device or a network device) to execute part or all of the steps in the methods of the above aspects.

[0013] In a ninth aspect, embodiments of the present application provide a computer program product, wherein the computer program product includes a non-transitory computer-readable storage medium storing a computer program, wherein the computer program is operable to cause a communication device (e.g., a terminal device or a network device) to perform some or all of the steps of the methods described in each of the above aspects. In some implementations, the computer program product can be a software installation package.

[0014] In the tenth aspect, an embodiment of the present application provides a chip, which includes a memory and a processor. The processor can call and run a computer program from the memory to implement some or all of the steps described in the methods of the above aspects.

[0015] Compared to the RRC message encapsulation method, MAC CE no longer requires upper-layer encapsulation. Therefore, in the present application, the use of the first MAC CE corresponding to the information in the first message used to indicate that the terminal device successfully transmitted the first data helps reduce the air interface overhead of transmitting the first message compared to the traditional method of transmitting the first message via RRC message. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] FIG1 is a wireless communication system 100 used in an embodiment of the present application.

[0017] FIG2A is a flow chart of a conventional four-step random access process.

[0018] FIG2B is a flowchart of a non-contention-based random access process.

[0019] FIG3 is a schematic flow chart of early data transmission (EDT).

[0020] FIG4 is a schematic flowchart of a wireless communication method according to an embodiment of the present application.

[0021] FIG5 is a schematic flowchart of an embodiment of the present application in which the first MAC CE is a null byte.

[0022] FIG6 is a schematic diagram of a contention resolution identifier MAC CE of a user equipment (UE) in an embodiment of the present application.

[0023] FIG7 is a schematic flowchart of the first MAC CE carrying the UE contention resolution identifier MAC CE in an embodiment of the present application.

[0024] FIG8 is a schematic flowchart of an embodiment of the present application in which the first message only includes a timing advance command MAC CE and a UE contention resolution identifier MAC CE.

[0025] FIG9 is a schematic diagram of a terminal device according to an embodiment of the present application.

[0026] FIG10 is a schematic diagram of a network device according to an embodiment of the present application.

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

[0028] The technical solution in this application will be described below with reference to the accompanying drawings.

[0029] Figure 1 illustrates a wireless communication system 100 used in an embodiment of the present application. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the terminal device 120 within the coverage area.

[0030] FIG1 exemplarily shows a network device and two terminals. Optionally, the wireless communication system 100 may include multiple network devices and each network device may include other numbers of terminal devices within its coverage area, which is not limited in the embodiments of the present application.

[0031] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0032] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0033] The terminal device in the embodiments of the present application may also be referred to as a UE, an access terminal, a user unit, a user station, a mobile station, a mobile station (MS), a mobile terminal (MT), a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent, or a user apparatus. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects, and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in V2X or D2D, etc. For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through the base station.

[0034] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. A base station can also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in device-to-device D2D, vehicle-to-everything (V2X), and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form adopted by the network device.

[0035] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0036] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device includes a CU and a DU. The gNB may also include an AAU.

[0037] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0038] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0039] Preconfigured uplink (ul) resources (PUR)

[0040] To further conserve energy, in some scenarios, communication systems support PUR transmission. PUR can be understood as a dedicated uplink resource that is allocated to a terminal device (e.g., a UE) by a network device (e.g., a base station) upon connection release. Terminal devices do not need to use a random access procedure before using PUR, and there is no contention or interference between terminal devices using PUR resources.

[0041] Random access process

[0042] In some protocols, two types of random access procedures are specified: 2-step random access channel (2-step RACH) and 4-step random access channel (4-step RACH). Among them, the 4-step RACH process was introduced in the LTE system and is also used in the NR system. The traditional 4-step random access process is introduced below in conjunction with Figure 2A. Usually, before initiating the RACH process, the terminal device can first obtain the physical random access channel (PRACH) resource configuration (time-frequency resources and code domain resources) from the system message or dedicated signaling. Afterwards, steps S210 to S240 can be executed.

[0043] In step S210, the terminal device sends a preamble to the network device. The preamble may be referred to as message 1 (Msg1) in the MAC layer protocol.

[0044] Typically, after sending a preamble, a reception window is set to wait for message 2 (Msg2) from the network device. The start and end times of the reception window are set based on configuration parameters. From the perspective of the network device, it is capable of distinguishing preambles received in different time-frequency domains, or different preambles in the same time-frequency domain. However, the network device cannot distinguish the same preamble sent by multiple terminal devices in the same time-frequency domain, resulting in an access conflict.

[0045] In some implementations, the network device may estimate the uplink synchronization (timing) and the approximate grant size required for the terminal device to transmit message 3 in step S230 based on the preamble.

[0046] In step S220 , the network device sends message 2 to the terminal device.

[0047] Typically, Message 2 may be a group message, that is, Message 2 may include a random access response (RAR) message to multiple terminal devices. The addressing information of Message 2 is contained in a group identifier called a random access network temporary identifier (RA-RNTI), which is used to identify the time domain resource information, frequency domain resource information, and carrier type information of the received preamble. The carrier type information is used to indicate whether the carrier of the preamble is a supplementary uplink (SUL) carrier or a non-supplementary uplink (NUL) carrier.

[0048] That is to say, a message 2 may include the RAR corresponding to the preamble received from the same carrier and the same time-frequency point. The RAR information element (IE) sent to each terminal device may include the temporary cell-radio network temporary identifier (T_C_RNTI) configured by the network device for the terminal device, the timing advance (for uplink synchronization), the uplink grant (UL-GRANT) for sending message 3 (message3, Msg3), and the index of the preamble received by the network device.

[0049] The receiving window mentioned above is also called an RAR window, and the terminal device monitors the physical downlink control channel (PDCCH) within the window to receive message 2, wherein the PDCCH is a PDCCH scrambled with RA-RNTI.

[0050] In some implementations, Message 2 may also include a backoff parameter to mitigate conflicts between preambles. If the terminal device decides to resend the preamble, it generates a random time based on the backoff parameter, such that the resent preamble is sent at least later than the generated random time.

[0051] In step S230, if the terminal device confirms that the network device has received the preamble code sent by itself, the terminal device sends message 3 to the network device based on UL-GRANT, also known as "scheduled transmission". Message 3 includes the terminal device identifier (also known as the terminal device identification (ID)).

[0052] Typically, a terminal device can determine whether the network device has received the preamble it sent based on the RA-RNTI and the preamble index in the RAR. If the terminal device confirms that the network device has received the preamble it sent, the terminal device sends message 3 based on the UL-GRANT, which includes at least the terminal device identifier (terminal device ID). The terminal device identifier carried in message 3 can resolve the contention conflict in step S240. Message 3 can be addressed using T_C_RNTI at the physical layer.

[0053] In some implementations, Message 3 is used to inform the network device of the event that triggered the RACH process. For example, if it is an initial access randomization process, Message 3 will carry the terminal device ID and the establishment cause; if it is an RRC reestablishment, it will carry the terminal device ID in the connected state and the establishment cause.

[0054] Afterwards, the terminal device may start a timer and, during the timer running, detect the downlink control channel PDCCH carrying message 4. If multiple terminal devices collide in step S210, then the conflict will continue to be sent in step S230 because multiple terminal devices will send message 3 based on the same UL-GRANT, but the terminal device identifiers included in the MAC CE of message 3 are different.

[0055] In step S240, if the network device correctly decodes message 3, the network device may send message 4 (Msg4) to the terminal device. This message is also called "contention resolution".

[0056] Typically, this message 4 is addressed using the T_C_RNTI in the received message 3, and the MAC CE therein includes the terminal device identifier included in the message 3 and a newly allocated C-RNTI.

[0057] Message 4 has two main functions: contention conflict resolution and transmission of RRC configuration information to the terminal device. If multiple terminal devices send message 3 on the same UL GRANT, the network device may be able to correctly decode one of them or may not be able to decode it (for example, when the interference levels between message 3 sent by multiple terminal devices are comparable). Therefore, when the terminal device receives message 4, if it finds that the T_C_RNTI convolved on the PDCCH matches the message 3 it sent, it will further check whether the MAC CE in the message 4 sent by the network device contains its own terminal device identifier. Afterwards, if message 4 contains its own terminal device identifier, the terminal device can confirm that the contention conflict has been resolved, that is, the random access process is completed, and use the newly allocated C-RNTI as its own identity. This identity is used for the addressing information of subsequent physical layer, MAC and RRC layer protocols.

[0058] The random access process described above in conjunction with Figure 2A can also be called a contention-based random access process (CBRA). Some protocols also introduce a non-contention or contention-free random access process (CFRA). Figure 2B shows a flowchart of the non-contention random access process. In the non-contention random access process, the network device can allocate specific random access resources to the terminal device. Accordingly, the network device can identify the specific terminal device through the random access preamble.

[0059] As shown in Figure 2B , the network device sends RA preamble assignment information to the terminal device. Subsequently, in response to the RA preamble assignment information, the terminal device may send a preamble to the network device. Accordingly, the MAC processing in the network device is the same as that in a contention-based random access process. After receiving the preamble, the network device may send a RAR to the terminal device. Accordingly, the processing in the terminal device is the same as that in a contention-based random access process.

[0060] EDT

[0061] During the EDT process, the terminal device may remain in an idle state, a suspended state, or an inactive state to complete the transmission of uplink and / or downlink small data packets. The process flow of the user plane transmission scheme of EDT is shown in Figure 3. The EDT transmission process diagram of Figure 3 includes steps S310 to S382.

[0062] In step S310, the terminal device sends an EDT request to the base station.

[0063] The EDT request is sent via an RRC message using the resources of Message 3 above, so the request can be called an RRC Early Data Request (RRCEarlyDataRequest). In addition to carrying small data, the EDT request can also carry signaling such as the request establishment reason and NAS layer dedicated information (dedicatedInfoNAS), and the NAS layer dedicated information includes small data.

[0064] In step S320, the base station sends initialization terminal equipment information (also called "initial UE message") to the mobility management entity (MME).

[0065] In step S330 , the MME and the serving gateway (S-GW) interact to perform operations related to modifying the bearer.

[0066] In step S340, the MME transmits uplink data to the S-GW.

[0067] In step S350, the S-GW transmits downlink data to the MME.

[0068] In step S361, the MME sends a downlink NAS transmission (DL_NAS TRANSPORT) to the base station.

[0069] In step S362, the MME sends a connection establishment indication (CONNECTION ESTABLISHMENT INDICATION) to the base station.

[0070] In step S370, the network device sends an RRC early data complete (RRCEarlyDataComplete) message to the terminal device.

[0071] The RRC early data completion message is sent through the resources of the above message 4. When the terminal device monitors message 4, it can confirm that the EDT data transmission is successful.

[0072] In step S381 , the base station interacts with the MME to perform a release process.

[0073] In step S382, the MME interacts with the S-GW to complete the bearer modification action.

[0074] In some scenarios, referring to the dotted portion of the process shown in FIG3 , the process may further include the transmission of a preamble (i.e., the transmission of Message 1) and / or the transmission of a RAR (i.e., the transmission of Message 2). In other scenarios, the process shown in FIG3 may also exclude the transmission of Message 1 and / or Message 2 to simplify the method flow shown in FIG3 .

[0075] In the above data transmission, the terminal device actually completes the transmission of small data packets without entering the connected state. This type of transmission is different from the mobile broadband (MBB) service that enters the connected state.

[0076] In terms of configuration, the network device will configure the size of the maximum transport block (TB) allowed to be transmitted by the current network through system information block 2 (SIB2). Accordingly, the terminal device determines the amount of data to be transmitted. If it is smaller than the maximum TB broadcasted, the terminal device can initiate EDT transmission; otherwise, the terminal device uses the normal connection establishment process to enter the connected state to transmit data.

[0077] In the above-mentioned EDT process, after the terminal device sends an RRC early data request and sends a small amount of data, the EDT transmission is considered successful only after receiving the RRC early data completion message sent by the network device. The current RRC message needs to be transmitted using a signaling radio bearer (SRB). During transmission, the SRB will be processed by the packet data convergence protocol (PDCP) layer and the radio link control (RLC) layer, such as adding a sequence number (SN), which increases some overhead. After entering the MAC layer, a MAC header must also be added, such as the SRB-related logical channel identification (LCID). All of this increases the overhead of the air interface.

[0078] Currently, in order to reduce uplink and downlink signaling overhead, some research (for example, the R19 Internet of Things (IoT) non-terrestrial network (NTN) research) plans to further enhance EDT features, for example, by introducing a more efficient Message 4 / RRC Early Data Completion message transmission mechanism.

[0079] In some scenarios, the network device sends a first message to the terminal device to indicate that the terminal device has successfully transmitted the first data. The first message is a radio resource control (RRC) message, and the air interface overhead required to transmit the RRC message is relatively large.

[0080] Taking the example of the first message including the RRC Early Data Complete message, in the EDT transmission process, when the network device successfully receives the first data sent by the terminal device, the network device will send an RRC Early Data Complete message to the terminal device, indicating that the first data transmission is successful. However, since the message is an RRC message, SRB transmission is used. As mentioned above, when the message is transmitted through SRB, on the one hand, it will be processed by the PDCP layer and the RLC layer, such as adding an SN to the message. On the other hand, after the message enters the MAC layer, a MAC header must be added to the message, for example, the MAC header carries the SRB-related LCID. These processes increase the air interface overhead required to transmit the message to a certain extent.

[0081] Therefore, to address the above issues, an embodiment of the present application proposes a wireless communication method to reduce the air interface overhead required for a network device to send a first message to a terminal device. The wireless communication method according to an embodiment of the present application is described below in conjunction with FIG4 . FIG4 is a schematic flow chart of the wireless communication method according to an embodiment of the present application. The method shown in FIG4 includes step S410.

[0082] In step S410, the network device sends a first message to the terminal device.

[0083] In some implementations, the first message includes information indicating that the terminal device has successfully transmitted the first data, or in other words, the first message includes information indicating that the terminal device has completed transmitting the first data, or in other words, the first message includes information indicating that the network device has successfully received the first data.

[0084] In some implementations, the first data may be the small data transmitted based on EDT as described above. Accordingly, the first message may be message 4 in EDT transmission. In some scenarios, the first message may also be called an "EarlyDataComplete message."

[0085] In the embodiment of the present application, there is no limitation on the transmission mode of the first message. In some implementations, the first message may be carried on the PDCCH, and accordingly, the terminal device may receive the first message by monitoring the PDCCH.

[0086] In the embodiments of the present application, the method for transmitting the first data is not limited. In some implementations, the first data can occupy the resources of message 3 for transmission. In other implementations, the first data can be carried in an RRCEarlyDataRequest message for transmission. For example, the RRCEarlyDataRequest message can include a NAS message carrying the first data.

[0087] In some implementations, the information indicating that the terminal device successfully transmitted the first data may correspond to MAC layer information. For example, the information indicating that the terminal device successfully transmitted the first data corresponds to the first MAC CE, or in other words, the information indicating that the terminal device successfully transmitted the first data is associated with the first MAC CE.

[0088] In some scenarios, if the first data is transmitted in EDT mode, the first MAC CE corresponds to information indicating EDT completion or success. Therefore, the first MAC CE can also be called "EDT complete MAC CE".

[0089] Compared to the RRC message encapsulation method, the MAC CE no longer requires upper-layer encapsulation. Therefore, in the embodiment of the present application, the use of the first MAC CE corresponding to the information in the first message used to indicate that the terminal device successfully transmitted the first data helps reduce the air interface overhead of transmitting the first message compared to the traditional method of transmitting the first message via an RRC message.

[0090] In some implementations, the information used to indicate that the terminal device has successfully transmitted the first data corresponds to the first MAC CE, which can be understood as the information used to indicate that the terminal device has successfully transmitted the first data is carried on the first MAC CE. In other implementations, the information used to indicate that the terminal device has successfully transmitted the first data corresponds to the first MAC CE, which can be understood as the information used to indicate that the terminal device has successfully transmitted the first data is not directly carried on the first MAC CE, but the information used to indicate that the terminal device has successfully transmitted the first data is indirectly indicated through the first MAC CE. For ease of understanding, this is described below in conjunction with Example 1, Example 2, and Example 3.

[0091] Embodiment 1: The first MAC CE is a null byte.

[0092] In some implementations, the first MAC CE is a null byte, or in other words, the first MAC CE is of null bit length. Typically, the size of such a MAC CE is 0 bits, which helps further reduce the air interface overhead required to transmit the first message. Of course, in the embodiments of the present application, the first MAC CE may not be a null byte.

[0093] In some implementations, the first MAC CE is associated with a first identifier, wherein the first identifier is used to identify the first MAC CE, or in other words, the first identifier indicates that the first MAC CE corresponds to information used to indicate that the terminal device successfully transmits the first data.

[0094] In some implementations, the first identifier may include an LCID or an extended LCID (eLCID).

[0095] In an embodiment of the present application, the first identifier associated with the first MAC CE may be determined based on predefined information or preconfigured information. Taking predefined information as an example, the first identifier associated with the first MAC CE may be defined in a communication protocol. In some implementations, the first message is a MAC protocol data unit (PDU), and the first identifier is carried in a subheader of the MAC PDU.

[0096] As described above, the first MAC CE is a null byte, which means that during the actual transmission process, the first MAC CE does not need to be transmitted, and the first MAC CE can be indicated by transmitting the first identifier. Accordingly, after receiving the first identifier, the terminal device can confirm the first MAC CE based on the first identifier.

[0097] In some implementations, the first message also includes a UE contention resolution identifier, which is carried in a second MAC CE and helps the terminal device determine whether the contention is resolved based on the first message. The second MAC CE is different from the first MAC CE.

[0098] Accordingly, if the terminal device determines that the UE contention resolution identifier in the second MAC CE matches itself, the terminal device can determine that the contention resolution is successful. Conversely, if the terminal device determines that the UE contention resolution identifier in the second MAC CE does not match itself, the terminal device can determine that the contention resolution has failed.

[0099] In an embodiment of the present application, there is no limitation on whether the UE contention resolution identifier in the second MAC CE matches itself. For example, if the first 48 bits of the common control channel (CCCH) service data unit (SDU) of the terminal device transmitting message 3 match the UE contention resolution identifier in the second MAC CE, then the UE contention resolution identifier in the second MAC CE matches the terminal device. Conversely, if the first 48 bits of the CCCH SDU of the terminal device transmitting message 3 do not match the UE contention resolution identifier in the second MAC CE, then the UE contention resolution identifier in the second MAC CE does not match the terminal device.

[0100] For ease of understanding, the following description is given with reference to FIG5 , taking the first MAC CE as a null byte as an example.

[0101] Referring to Figure 5 , assuming the terminal device is a UE and the network device is a base station, first data is transmitted via an EDT, the first identifier is LCID1, and the first MAC CE is an EDT completion MAC CE. The base station sends a first message to the UE using resources in Msg4. The first message is Msg4, LCID1 is carried in the subheader of the MAC PDU corresponding to Msg4, and LCID1 is associated with the EDT completion MAC CE. The EDT completion MAC CE has a fixed size of 0 bits. The method shown in Figure 5 includes steps S510 and S520.

[0102] In step S510, the UE uses Msg3 resources to send an RRC EarlyDataRequest message, where the RRC EarlyDataRequest message carries a NAS message including the first data.

[0103] In step S520, the base station sends Msg4 to the UE. Accordingly, the UE monitors the PDCCH to receive Msg4. If the UE successfully decodes the MAC PDU and the MAC PDU includes LCID1, the UE considers that the first data transmission is successful.

[0104] Embodiment 2: The first MAC CE carries a UE contention resolution identifier.

[0105] In some implementations, the first MAC CE carries the UE contention resolution identifier, that is, the MAC CE corresponding to the information used to indicate that the terminal device successfully transmits the first data and the MAC CE carrying the UE contention resolution identifier are both one MAC CE, namely the first MAC CE.

[0106] In some scenarios, the first MAC CE may also be referred to as "UE contention resolution identity & EDT complete MAC CE".

[0107] In some implementations, the information used to indicate that the terminal device has successfully transmitted the first data may not be directly carried in the first MAC CE. In this case, the first MAC CE may only include a UE contention resolution identifier. That is to say, in the embodiment of the present application, although the first MAC CE may also correspond to the information used to indicate that the terminal device has successfully transmitted the first data, the number of bytes contained in the first MAC CE is similar to or the same as the number of bytes contained in the MAC CE that only carries the UE contention resolution identifier, and does not increase the length of the MAC CE, which helps to avoid increasing the air interface overhead required to transmit the first MAC CE. Of course, in the embodiment of the present application, the first MAC CE can directly carry the UE contention resolution identifier and the information used to indicate that the terminal device has successfully transmitted the first data.

[0108] In some implementations, the first MAC CE is associated with a first identifier, wherein the first identifier is used to identify the first MAC CE, or in other words, the first identifier indicates that the first MAC CE corresponds to a UE contention resolution identifier and is used to indicate information that the terminal device successfully transmits the first data.

[0109] As described above, the first MAC CE does not directly carry information indicating that the terminal device successfully transmitted the first data. In this case, the terminal device can determine, based on the first identifier, that the first MAC CE corresponds to information indicating that the terminal device successfully transmitted the first data. Therefore, without increasing the length of the MAC CE, the first MAC CE in this embodiment of the present application can correspond to the UE contention resolution identifier and the information indicating that the terminal device successfully transmitted the first data.

[0110] In some implementations, the first identifier may include an LCID or an eLCID.

[0111] In an embodiment of the present application, the first identifier associated with the first MAC CE may be determined based on predefined information or preconfigured information. Taking predefined information as an example, the first identifier associated with the first MAC CE may be defined in a communication protocol. In some implementations, the first message is a MAC PDU, and the first identifier is carried in a subheader of the MAC PDU.

[0112] In some implementations, if the terminal device determines that the UE contention resolution identifier in the first MAC CE matches the terminal device, the terminal device may determine that contention resolution is successful and the first data transmission is successful. Conversely, if the terminal device determines that the UE contention resolution identifier in the second MAC CE does not match the terminal device, the terminal device may determine that contention resolution has failed and the first data transmission has failed.

[0113] In the embodiment of the present application, there is no limitation on whether the UE contention resolution identifier in the first MAC CE matches the UE contention resolution identifier in the first MAC CE. For example, if the first 48 bits of the CCCH SDU of the terminal device transmitting message 3 match the UE contention resolution identifier in the first MAC CE, then the UE contention resolution identifier in the first MAC CE matches the terminal device. Conversely, if the first 48 bits of the CCCH SDU of the terminal device transmitting message 3 do not match the UE contention resolution identifier in the first MAC CE, then the UE contention resolution identifier in the first MAC CE does not match the terminal device.

[0114] For ease of understanding, the following describes the UE contention resolution identifier & EDT completion MAC CE according to an embodiment of the present application in conjunction with Figures 6 and 7. Referring to Figure 6, the UE contention resolution identifier & EDT completion MAC CE may include only the UE contention resolution identifier, which may occupy 6 bytes, with one byte comprising 8 bits. That is, the UE contention resolution identifier & EDT completion MAC CE occupy a total of 48 bits.

[0115] Referring to Figure 7 , assuming that the terminal device is a UE and the network device is a base station, the first data is transmitted via EDT, the first identifier is LCID2, and the first MAC CE is the UE contention resolution identifier & EDT completion MAC CE. The base station sends a first message to the UE using the resources of Msg4, and the first message is Msg4. LCID2 is carried in the subheader of the MAC PDU corresponding to Msg4, and LCID2 is used to identify the UE contention resolution identifier & EDT completion MAC CE. Figure 7 includes steps S710 and S720.

[0116] In step S710, the UE uses Msg3 resources to send an RRC EarlyDataRequest message, where the NAS message of the message carries the first data.

[0117] In step S720, the base station sends Msg4 to the UE. Accordingly, the UE monitors the PDCCH to receive Msg4. If the UE successfully decodes the MAC PDU, where the MAC PDU contains LCID2, and the UE contention resolution identifier in the first MAC CE obtained after decoding matches the first 48 bits of the CCCH SDU transmitted in Msg3, the UE considers that the contention is successful and the first data transmission is successful.

[0118] In some scenarios, the terminal device can directly use the resources of message 3 to transmit the first data. In this scenario, the terminal device needs to maintain uplink synchronization to increase the possibility of successfully transmitting the first data. At this time, how the terminal device maintains uplink synchronization is an urgent problem to be solved.

[0119] To address the above issues, in an embodiment of the present application, the TA information of the terminal device can be carried in the first message, so that the TA value of the terminal device remains valid during subsequent data transmission processes. In other words, during the Nth data transmission process, the TA value of the terminal device is maintained valid by the TA information carried in the first message during the N-1th data transmission process.

[0120] In the embodiment of the present application, the introduction to the first message can be found above, and for the sake of brevity, it will not be repeated here.

[0121] In some implementations, the TA information may be carried in a MAC CE (also referred to as a "third MAC CE"). Accordingly, the third MAC CE may also be referred to as a timing advance command MAC CE (TA command MAC CE).

[0122] As described above, network devices can help terminal devices update their TAs to maintain uplink synchronization by sending TA information. In other scenarios, even if the terminal device does not need to adjust its TA, the network device can still send TA information to the terminal device. Accordingly, the TA adjustment value in the TA information can be 0. In this case, the TA information indicates to the terminal device that its current TA is valid.

[0123] In some implementations, the first message may include a fourth MAC CE, which is used to carry a UE contention resolution identifier, so that the terminal device can determine whether contention resolution is successful based on the fourth MAC CE, or in other words, so that the terminal device can determine whether the first message is sent to itself. The structure of the fourth MAC CE can be shown in Figure 6.

[0124] In some scenarios, the fourth MAC CE may also be referred to as “UE contention resolution identity MAC CE”.

[0125] In some implementations, if the terminal device determines that the UE contention resolution identifier in the fourth MAC CE matches the terminal device, the terminal device may determine that contention resolution is successful and the first data transmission is successful. Conversely, if the terminal device determines that the UE contention resolution identifier in the fourth MAC CE does not match the terminal device, the terminal device may determine that contention resolution has failed and the first data transmission has failed.

[0126] In this embodiment of the present application, there is no limitation on the manner in which the UE contention resolution identifier in the fourth MAC CE matches itself. For example, if the first 48 bits of the CCCH SDU of the terminal device transmitting message 3 match the UE contention resolution identifier in the fourth MAC CE, then the UE contention resolution identifier in the fourth MAC CE matches the terminal device. Conversely, if the first 48 bits of the CCCH SDU of the terminal device transmitting message 3 do not match the UE contention resolution identifier in the fourth MAC CE, then the UE contention resolution identifier in the fourth MAC CE does not match the terminal device.

[0127] In some scenarios, the MAC CE included in the first message may include only the third MAC CE and the fourth MAC CE. Compared to the traditional message 4, this helps reduce the information content carried in the first message, thereby reducing the air interface overhead required to transmit the first message. Of course, in the embodiment of the present application, if the above issue is not considered, the first message may also carry other information.

[0128] It should be noted that, in the embodiment of the present application, during the transmission process of the first data (for example, in the EDT used to transmit the first data), Message 1 and / or Message 2 may no longer be transmitted. In other words, the terminal device may directly transmit the first data on the resources of Message 3 to save the overhead required for the transmission process of the first data. Of course, in the embodiment of the present application, the transmission process of the first data (for example, in the EDT used to transmit the first data) may include the process of transmitting Message 1 and / or Message 2.

[0129] For ease of understanding, the following description is given with reference to FIG8 , taking the case where the first message only includes the third MAC CE and the fourth MAC CE as an example.

[0130] Referring to Figure 8 , assuming the terminal device is a UE and the network device is a base station, first data is transmitted via the EDT, and the base station sends a first message to the UE using the resources of Msg4. The first message is Msg4, the third MAC CE in Msg4 is the TAC MAC CE, and the fourth MAC CE is the UE Contention Resolution Identifier MAC CE. The identifiers LCID3 and LCID4 in Msg4 are carried in the subheader of the MAC PDU, where LCID3 is associated with the TAC MAC CE and LCID4 is associated with the UE Contention Resolution Identifier MAC CE. Figure 8 includes steps S810 and S820.

[0131] In step S810, the UE uses Msg3 resources to send an RRC EarlyDataRequest message, where the RRC EarlyDataRequest message carries a NAS message including the first data.

[0132] In step S820, the base station sends Msg4 to the UE. Accordingly, the UE monitors the PDCCH to receive Msg4. If the UE successfully decodes the MAC PDU and the UE contention resolution identifier in the UE contention resolution identifier MAC CE matches the first 48 bits of the CCCH SDU transmitted in Msg3, the UE considers that the contention resolution is successful and the first data transmission is successful.

[0133] In addition, the UE can adjust the TA based on the TAC MAC CE to maintain uplink synchronization, so as to improve the success rate of the next transmission of the first data through the Msg3 resource.

[0134] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 8 . The device embodiment of the present application is described in detail below in conjunction with Figures 9 to 11 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for portions not described in detail, reference can be made to the above method embodiment.

[0135] FIG9 is a schematic diagram of a terminal device according to an embodiment of the present application. The terminal device 900 shown in FIG9 includes: a receiving unit 910 .

[0136] The receiving unit 910 is used to receive a first message sent by a network device, where the first message includes information for indicating that the terminal device has successfully transmitted the first data, wherein the first message satisfies one or more of the following: the first message carries the timing advance TA information of the terminal device; the information for indicating that the terminal device has successfully transmitted the first data corresponds to a first media access control MAC control element CE.

[0137] In some implementations, the first MAC CE is a null byte or null bit length.

[0138] In some implementations, the first message further includes a user equipment UE contention resolution identifier, and the UE contention resolution identifier is carried in the second MAC CE.

[0139] In some implementations, the first MAC CE is associated with a first identifier, and the first identifier is used to indicate that the first MAC CE corresponds to the information used to indicate that the terminal device has successfully transmitted the first data.

[0140] In some implementations, the first MAC CE carries a UE contention resolution identifier.

[0141] In some implementations, the first MAC CE is associated with a first identifier, and the first identifier is used to indicate that the first MAC CE corresponds to a UE contention resolution identifier and is used to indicate information that the terminal device successfully transmits the first data.

[0142] In some implementations, the first message is a MAC protocol data unit (PDU), and the first identifier associated with the first MAC CE is carried in a subheader of the MAC PDU.

[0143] In some implementations, the timing advance TA information of the terminal device is carried on a third MAC CE, the first message only includes the third MAC CE and the fourth MAC CE, and the fourth MAC CE is used to carry a UE contention resolution identifier.

[0144] In some implementations, the first message includes a UE contention resolution identifier. If the UE contention resolution identifier matches the terminal device, the first data transmission is successful.

[0145] In some implementations, the first data is transmitted via an early data transmission (EDT).

[0146] FIG10 is a schematic diagram of a network device according to an embodiment of the present application. The network device shown in FIG10 includes: a sending unit 1010 .

[0147] The sending unit 1010 is used to send a first message to a terminal device, where the first message includes information for indicating that the terminal device has successfully transmitted the first data, wherein the first message satisfies one or more of the following: the first message carries the timing advance TA information of the terminal device; the information for indicating that the terminal device has successfully transmitted the first data corresponds to a first media access control MAC control element CE.

[0148] In some implementations, the first MAC CE is a null byte or null bit length.

[0149] In some implementations, the first message further includes a user equipment UE contention resolution identifier, and the UE contention resolution identifier is carried in the second MAC CE.

[0150] In some implementations, the first MAC CE is associated with a first identifier, and the first identifier is used to indicate that the first MAC CE corresponds to the information used to indicate that the terminal device has successfully transmitted the first data.

[0151] In some implementations, the first MAC CE carries a UE contention resolution identifier.

[0152] In some implementations, the first MAC CE is associated with a first identifier, and the first identifier is used to indicate that the first MAC CE corresponds to a UE contention resolution identifier and is used to indicate information that the terminal device successfully transmits the first data.

[0153] In some implementations, the first message is a MAC protocol data unit (PDU), and the first identifier associated with the first MAC CE is carried in a subheader of the MAC PDU.

[0154] In some implementations, the timing advance TA information of the terminal device is carried on a third MAC CE, the first message only includes the third MAC CE and the fourth MAC CE, and the fourth MAC CE is used to carry a UE contention resolution identifier.

[0155] In some implementations, the first message includes a UE contention resolution identifier. If the UE contention resolution identifier matches the terminal device, the first data transmission is successful.

[0156] In some implementations, the first data is transmitted via an early data transmission (EDT).

[0157] In an optional embodiment, the receiving unit 910 may be a transceiver 1130. The terminal device 900 may further include a processor 1110 and a memory 1120, as specifically shown in FIG11 .

[0158] In an optional embodiment, the sending unit 1010 may be a transceiver 1130. The network device 1000 may further include a processor 1110 and a memory 1120, as specifically shown in FIG11 .

[0159] Figure 11 is a schematic block diagram of a communication device according to an embodiment of the present application. The dashed lines in Figure 11 indicate that the unit or module is optional. The device 1100 may be used to implement the method described in the above method embodiment. The device 1100 may be a chip, a terminal device, or a network device.

[0160] The device 1100 may include one or more processors 1110. The processor 1110 may support the device 1100 to implement the method described in the method embodiment above. The processor 1110 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0161] The apparatus 1100 may further include one or more memories 1120. The memories 1120 store programs that can be executed by the processor 1110, causing the processor 1110 to perform the methods described in the above method embodiments. The memories 1120 may be independent of the processor 1110 or integrated into the processor 1110.

[0162] The apparatus 1100 may further include a transceiver 1130. The processor 1110 may communicate with other devices or chips via the transceiver 1130. For example, the processor 1110 may transmit and receive data with other devices or chips via the transceiver 1130.

[0163] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal or network device provided in the present application, and the program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0164] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to a terminal or network device provided in the present application, and the program causes a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0165] The embodiments of the present application also provide a computer program. The computer program can be applied to the terminal or network device provided in the embodiments of the present application, and the computer program enables a computer to execute the method performed by the terminal or network device in each embodiment of the present application.

[0166] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0167] In the embodiments of this application, the term "indication" may refer to a direct indication, an indirect indication, or an indication of an association. For example, "A indicates B" may refer to a direct indication of B, e.g., B can obtain information through A; it may refer to an indirect indication of B, e.g., A indicates C, e.g., B can obtain information through C; or it may refer to an association between A and B.

[0168] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0169] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0170] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0171] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0172] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean 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 the present application.

[0173] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0174] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0175] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0176] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0177] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A wireless communication method, characterized in that: include: The terminal device receives a first message sent by the network device, where the first message includes information indicating that the terminal device successfully transmits the first data, wherein the first message satisfies one or more of the following conditions: The first message carries timing advance TA information of the terminal device; The information used to indicate that the terminal device has successfully transmitted the first data corresponds to the first media access control MAC control element CE.

2. The method according to claim 1, wherein The first MAC CE is a null byte or null bit length.

3. The method according to claim 2, wherein The first message further includes a user equipment UE contention resolution identifier, and the UE contention resolution identifier is carried in the second MAC CE.

4. The method according to any one of claims 1 to 3, wherein The first MAC CE is associated with a first identifier, and the first identifier is used to indicate that the first MAC CE corresponds to the information used to indicate that the terminal device has successfully transmitted the first data.

5. The method according to claim 1, wherein The first MAC CE carries a UE contention resolution identifier.

6. The method according to claim 1 or 5, wherein: The first MAC CE is associated with a first identifier, and the first identifier is used to indicate that the first MAC CE corresponds to a UE contention resolution identifier and is used to indicate information that the terminal device successfully transmits the first data.

7. The method according to any one of claims 1 to 6, wherein The first message is a MAC protocol data unit (PDU), and the first identifier associated with the first MAC CE is carried in the subheader of the MAC PDU.

8. The method according to claim 1, wherein The timing advance TA information of the terminal device is carried on the third MAC CE, and the first message only includes the third MAC CE and the fourth MAC CE, and the fourth MAC CE is used to carry the UE contention resolution identifier.

9. The method according to any one of claims 1 to 8, wherein The first message includes a UE contention resolution identifier. If the UE contention resolution identifier matches the terminal device, the first data transmission is successful.

10. The method according to any one of claims 1 to 9, wherein The first data is transmitted via early data transmission (EDT).

11. A wireless communication method, characterized in that: include: The network device sends a first message to the terminal device, where the first message includes information indicating that the terminal device successfully transmits the first data, wherein the first message satisfies one or more of the following conditions: The first message carries timing advance TA information of the terminal device; The information used to indicate that the terminal device has successfully transmitted the first data corresponds to the first media access control MAC control element CE.

12. The method according to claim 11, wherein The first MAC CE is a null byte or null bit length.

13. The method according to claim 12, wherein: The first message further includes a user equipment UE contention resolution identifier, and the UE contention resolution identifier is carried in the second MAC CE.

14. The method according to any one of claims 11 to 13, wherein The first MAC CE is associated with a first identifier, and the first identifier is used to indicate that the first MAC CE corresponds to the information used to indicate that the terminal device has successfully transmitted the first data.

15. The method according to claim 11, wherein The first MAC CE carries a UE contention resolution identifier.

16. The method according to claim 11 or 15, wherein: The first MAC CE is associated with a first identifier, and the first identifier is used to indicate that the first MAC CE corresponds to a UE contention resolution identifier and is used to indicate information that the terminal device successfully transmits the first data.

17. The method according to any one of claims 11 to 16, wherein: The first message is a MAC protocol data unit (PDU), and the first identifier associated with the first MAC CE is carried in the subheader of the MAC PDU.

18. The method according to claim 11, wherein The timing advance TA information of the terminal device is carried on the third MAC CE, and the first message only includes the third MAC CE and the fourth MAC CE, and the fourth MAC CE is used to carry the UE contention resolution identifier.

19. The method according to any one of claims 11 to 18, wherein The first message includes a UE contention resolution identifier. If the UE contention resolution identifier matches the terminal device, the first data transmission is successful.

20. The method according to any one of claims 11 to 19, wherein The first data is transmitted via early data transmission (EDT).

21. A terminal device, characterized in that: include: A receiving unit, configured to receive a first message sent by a network device, where the first message includes information indicating that the terminal device successfully transmits the first data, wherein the first message satisfies one or more of the following conditions: The first message carries timing advance TA information of the terminal device; The information used to indicate that the terminal device has successfully transmitted the first data corresponds to the first media access control MAC control element CE.

22. The terminal device according to claim 21, wherein: The first MAC CE is a null byte or null bit length.

23. The terminal device according to claim 22, wherein: The first message further includes a user equipment UE contention resolution identifier, and the UE contention resolution identifier is carried in the second MAC CE.

24. The terminal device according to any one of claims 21 to 23, characterized in that: The first MAC CE is associated with a first identifier, and the first identifier is used to indicate that the first MAC CE corresponds to the information used to indicate that the terminal device has successfully transmitted the first data.

25. The terminal device according to claim 21, wherein: The first MAC CE carries a UE contention resolution identifier.

26. The terminal device according to claim 21 or 25, characterized in that: The first MAC CE is associated with a first identifier, and the first identifier is used to indicate that the first MAC CE corresponds to a UE contention resolution identifier and is used to indicate information that the terminal device successfully transmits the first data.

27. The terminal device according to any one of claims 21 to 26, characterized in that: The first message is a MAC protocol data unit (PDU), and the first identifier associated with the first MAC CE is carried in the subheader of the MAC PDU.

28. The terminal device according to claim 21, wherein: The timing advance TA information of the terminal device is carried on the third MAC CE, and the first message only includes the third MAC CE and the fourth MAC CE, and the fourth MAC CE is used to carry the UE contention resolution identifier.

29. The terminal device according to any one of claims 21 to 28, characterized in that: The first message includes a UE contention resolution identifier. If the UE contention resolution identifier matches the terminal device, the first data transmission is successful.

30. The terminal device according to any one of claims 21 to 29, characterized in that: The first data is transmitted via early data transmission (EDT).

31. A network device, characterized in that: include: A sending unit, configured to send a first message to a terminal device, where the first message includes information indicating that the terminal device has successfully transmitted the first data, wherein the first message satisfies one or more of the following conditions: The first message carries timing advance TA information of the terminal device; The information used to indicate that the terminal device has successfully transmitted the first data corresponds to the first media access control MAC control element CE.

32. The network device according to claim 31, wherein: The first MAC CE is a null byte or null bit length.

33. The network device according to claim 32, wherein: The first message further includes a user equipment UE contention resolution identifier, and the UE contention resolution identifier is carried in the second MAC CE.

34. The network device according to any one of claims 31 to 33, wherein: The first MAC CE is associated with a first identifier, and the first identifier is used to indicate that the first MAC CE corresponds to the information used to indicate that the terminal device has successfully transmitted the first data.

35. The network device according to claim 31, wherein The first MAC CE carries a UE contention resolution identifier.

36. The network device according to claim 31 or 35, wherein: The first MAC CE is associated with a first identifier, and the first identifier is used to indicate that the first MAC CE corresponds to a UE contention resolution identifier and is used to indicate information that the terminal device successfully transmits the first data.

37. The network device according to any one of claims 31 to 36, wherein: The first message is a MAC protocol data unit (PDU), and the first identifier associated with the first MAC CE is carried in the subheader of the MAC PDU.

38. The network device according to claim 31, wherein: The timing advance TA information of the terminal device is carried on the third MAC CE, and the first message only includes the third MAC CE and the fourth MAC CE, and the fourth MAC CE is used to carry the UE contention resolution identifier.

39. The network device according to any one of claims 31 to 38, wherein: The first message includes a UE contention resolution identifier. If the UE contention resolution identifier matches the terminal device, the first data transmission is successful.

40. The network device according to any one of claims 31 to 39, wherein: The first data is transmitted via early data transmission (EDT).

41. A terminal device, characterized in that: The terminal comprises a transceiver, a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory and control the transceiver to receive or send a signal, so that the terminal executes the method according to any one of claims 1 to 10.

42. A network device, characterized in that: The network device comprises a transceiver, a memory and a processor, wherein the memory is used to store a program, and the processor is used to call the program in the memory and control the transceiver to receive or send a signal, so that the network device executes the method according to any one of claims 11 to 20.

43. A device, characterized in that The device comprises a processor configured to call a program from a memory so as to enable the device to execute the method according to any one of claims 1 to 20.

44. A chip, characterized in that The device comprises a processor configured to call a program from a memory so that a device equipped with the chip executes the method according to any one of claims 1 to 20.

45. A computer-readable storage medium, characterized in that A program is stored thereon, and the program causes a computer to execute the method according to any one of claims 1 to 20.

46. ​​A computer program product, characterized in that The method comprises a program for causing a computer to execute the method according to any one of claims 1 to 20.

47. A computer program, characterized in that The computer program causes a computer to execute the method according to any one of claims 1 to 20.

Images