Data transmission method and communication apparatus

By receiving and sending a second message carrying contention result information during data transmission, and utilizing frequency and time domain indicators, the transmission and decoding efficiency problems caused by the omission of MSG1 and MSG2 are solved, achieving efficient data transmission and fast contention result identification.

WO2026232985A1PCT designated stage Publication Date: 2026-11-12HONOR DEVICE CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2026/084339
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2025-05-09
Filing Date
2026-03-18
Publication Date
2026-11-12

AI Technical Summary

Technical Problem

In the data transmission process, the transmission of MSG1 and MSG2 is omitted in the existing technology, which makes the design of message 4 an urgent problem to be solved, affecting the transmission efficiency and decoding efficiency.

Method used

The network device receives a first message sent by multiple user equipments at the same time and/or frequency domain location, and sends a second message containing contention result information. The subheader of the message body carries frequency and time domain indication fields, enabling user equipment to quickly identify contention result information and improve transmission and decoding efficiency.

Benefits of technology

It significantly improves data transmission and decoding efficiency, reduces signaling overhead, and increases the speed of identifying competition result information.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2026084339_12112026_PF_FP_ABST
    Figure CN2026084339_12112026_PF_FP_ABST
Patent Text Reader

Abstract

Provided are a data transmission method and a communication apparatus. The method is applied to the field of communications. For example, the method is applied to a communication system supporting NTNs. In the embodiments of the present application, a network device receives first messages sent by a plurality of UEs in a same time domain and / or a same frequency domain, and then responds to the first messages from the plurality of UEs by means of one second message. Compared with sending a response for each first message, multiplexing responses to a plurality of first messages into a same message (e.g., a second message) for sending can significantly improve the transmission efficiency. In addition, in the embodiments of the present application, a sub-header of a message body carries a frequency-domain indication field and / or a time-domain indication field, such that a UE can quickly determine whether certain information included in the second message is contention result information for itself, thereby improving the decoding efficiency.
Need to check novelty before this filing date? Find Prior Art

Description

Methods and communication devices for data transmission

[0001] This application claims priority to Chinese Patent Application No. 202510604496.1, filed on May 9, 2025, entitled "Method and Communication Apparatus for Data Transmission", the entire contents of which are incorporated herein by reference. Technical Field

[0002] This application relates to the field of communications, and more specifically, to a method and communication apparatus for data transmission. Background Technology

[0003] Data transmission methods include early data transmission (EDT), which allows data transmission during random access without requiring the UE to transition to connected state. The user equipment (UE) transmits uplink data via a third message (e.g., RRCEarlyDataRequest or RRCConnectionResumeRequest). Upon receiving the third message, the network responds with a fourth message (RRCEarlyDataComplete or RRCConnectionRelease). However, this data transmission includes the transmission of message 1 (MSG1) and message 2 (MSG2) (which may include a random access response (RAR) message). To further improve data transmission efficiency, based on this EDT mechanism, the data transmission process may omit the transmission of MSG1 and MSG2 (RAR). Instead, using shared resources configured on the network side, the UE directly sends MSG3, carrying the user's uplink data.

[0004] In the aforementioned data transmission process, omitting MSG1 and MSG2 (RAR) can significantly reduce signaling overhead. However, how to design message 4 under these circumstances becomes a pressing issue. Summary of the Invention

[0005] In view of this, this application provides a method, communication device, chip system, computer-readable storage medium, computer program product, and communication system for data transmission. By designing multiplexed messages for multiple UEs, not only can transmission efficiency be improved, but also the UE can quickly know whether a certain information included in the second message is information about the competition result for itself, thereby improving decoding efficiency.

[0006] In a first aspect, a method for data transmission is provided. This method 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 this approach.

[0007] Specifically, the method includes: a network device receiving first messages (e.g., CB MSG3) sent by multiple UEs at the same time domain location and / or the same frequency domain location, the first messages being used to transmit uplink data; and sending a second message (e.g., a MAC message or MSG4), the second message including information notifying the multiple UEs of the contention result. Compared to the network device sending a separate response message for each UE, the network device can significantly improve transmission efficiency by multiplexing the responses of multiple first messages into a single message (e.g., the second message).

[0008] Furthermore, in this embodiment of the application, the frequency domain indicator field and / or time domain indicator field are carried in the sub-header of the message body, so that the UE can quickly know whether a certain information included in the second message is information about the competition result against itself, which can improve decoding efficiency.

[0009] In one possible implementation, the second message is a MAC PDU; the MAC PDU includes one or more of the following: a MAC sub-PDU for fallback, the MAC sub-header of the fallback MAC sub-PDU including one or more of the following indication fields: a first frequency domain indication field, a first time domain indication field, and a first orthogonal coverage code (OCC) indication field; the first frequency domain indication field is used to indicate the frequency domain information corresponding to the UE performing the fallback operation among the plurality of UEs; the first time domain indication field is used to indicate the time domain information corresponding to the UE performing the fallback operation among the plurality of UEs; the first OCC indication field is used to indicate the OCC sequence adopted by the UE performing the fallback operation among the plurality of UEs;

[0010] One or more MAC sub-PDUs are used to carry the contention result, wherein the MAC subheader of each MAC sub-PDU includes one or more of the following: a second frequency domain indication field, a second time domain indication field, a length indication field, and a second OCC indication field; the second frequency domain indication field is used to indicate the frequency domain information corresponding to the UE that successfully competed, or the frequency domain information corresponding to the UE related to the contention result; the second time domain indication field is used to indicate the time domain information corresponding to the UE that successfully competed, or the time domain information corresponding to the UE related to the contention result; the length indication field is used to indicate the length information of the data decoding that the UE needs to skip; the second OCC indication field is used to indicate the OCC sequence adopted by the UE that successfully competed, or the OCC sequence adopted by the UE related to the contention result;

[0011] A MAC sub-PDU for backoff (BI) includes a MAC sub-header comprising one or more of the following indication fields: a third frequency domain indication field, a third time domain indication field, and a third OCC indication field; the third frequency domain indication field indicates the frequency domain information corresponding to the UE performing the backoff operation among the plurality of UEs; the third time domain indication field indicates the time domain information corresponding to the UE performing the backoff operation among the plurality of UEs; and the third OCC indication field indicates the OCC sequence adopted by the UE performing the backoff operation among the plurality of UEs.

[0012] One or more MAC SDUs and / or MAC CEs are associated with the one or more MAC sub-PDUs used to carry the competition results.

[0013] There are three scenarios for sending the first message at the same time domain location and / or the same frequency domain location. Correspondingly, there are also corresponding implementation methods for multiplexing the second message in each scenario. These will be described separately below.

[0014] Scenario 1: In some embodiments, the network device receives a first message sent by multiple UEs at different frequency domain locations at the same time domain location; wherein, the one or more MAC sub-PDUs used to carry the contention result include a first MAC sub-PDU, and the MAC sub-header of the first MAC sub-PDU includes a second frequency domain indication field and / or the length indication field; the second frequency domain indication field is used to indicate the first frequency domain information.

[0015] Therefore, in Case 1, the network device configures the second frequency domain indication domain and / or the length indication domain so that the UE can perform a judgment based on the frequency domain information indicated by the second frequency domain indication domain to obtain a judgment result on whether the first MAC sub-PDU is related to itself; and, if it is determined that the first MAC sub-PDU is not related, it can also skip the data decoding of the corresponding length based on the length indication domain, which helps to improve decoding efficiency.

[0016] Optionally, when the plurality of UEs transmit the first message using an orthogonal coverage code (OCC) sequence, the MAC subheader of the first MAC sub-PDU further includes a second OCC indication field. This second OCC indication field indicates a first OCC sequence. The first OCC sequence represents the OCC sequence corresponding to the UE that successfully competes among the plurality of UEs, or it represents the OCC sequence corresponding to the UE associated with the first MAC sub-PDU among the plurality of UEs. Therefore, in scenarios where OCC is applied, the network device can also configure a second OCC indication field, enabling the UE to perform a judgment based on the frequency domain information indicated by the second frequency domain indication field and the OCC sequence indicated by the second OCC indication field.

[0017] Optionally, the first MAC sub-PDU includes a contention success RAR; or, the first MAC sub-PDU is a contention resolution MAC CE.

[0018] In scenario 1, in one possible implementation, the MAC sub-header of the MAC sub-PDU for fallback includes the first frequency domain indication field, which indicates second frequency domain information. Therefore, in scenario 1, by configuring the first frequency domain indication field in the MAC sub-header of the MAC sub-PDU for fallback, the network device enables the UE to perform a judgment based on the frequency domain information indicated by the first frequency domain indication field to obtain a judgment result regarding whether the MAC sub-PDU for fallback is related to itself.

[0019] Optionally, when multiple UEs transmit the first message at different frequency domain locations at the same time domain location using orthogonal coverage code (OCC) sequences, the MAC subheader of the MAC sub-PDU for rollback further includes the first OCC indication field. The first OCC indication field is used to indicate a second OCC sequence, which represents the OCC sequence used by the UE performing the rollback operation. Therefore, in scenarios where OCC is applied, the network device configures the first frequency domain indication field and the first OCC indication field in the MAC subheader of the MAC sub-PDU for rollback, enabling the UE to perform a joint judgment based on the frequency domain information indicated by the first frequency domain indication field and the OCC sequence indicated by the first OCC indication field, to obtain a judgment result on whether the MAC sub-PDU for rollback is related to itself.

[0020] Optionally, the MAC sub-PDU for rollback includes a rollback RAR; or, the MAC sub-PDU for rollback is a MAC CE for rollback.

[0021] Scenario 2: In some embodiments, the network device receives a first message sent by multiple UEs at different time domain locations in the same frequency domain; wherein, the one or more MAC sub-PDUs used to carry the contention result include a second MAC sub-PDU, and the MAC sub-header of the second MAC sub-PDU includes the second time domain indication field and / or the length indication field; the second time domain indication field is used to indicate the first time domain information.

[0022] Therefore, in scenario 2, the network device configures a second time domain indication field and / or the length indication field in the MAC subheader of the second MAC sub-PDU, enabling the UE to perform a judgment based on the time domain information indicated by the second time domain indication field to obtain a judgment result on whether the second MAC sub-PDU is related to itself; and, if it is determined that the second MAC sub-PDU is not related, it can also skip the data decoding of the corresponding length based on the length indication field, which helps to improve decoding efficiency.

[0023] Optionally, when the plurality of UEs transmit the first message using an orthogonal coverage code (OCC) sequence, the MAC subheader of the second MAC sub-PDU further includes a second OCC indication field. The second OCC indication field indicates a third OCC sequence. The third OCC sequence represents the OCC sequence corresponding to the UE associated with the second MAC sub-PDU among the plurality of UEs, or the OCC sequence corresponding to the UE that successfully competes for the rights among the plurality of UEs. Therefore, in scenarios where OCC is applied, the network device can also configure a second OCC indication field, enabling the UE to perform a judgment based on the time-domain information indicated by the second time-domain indication field and the OCC sequence indicated by the second OCC indication field.

[0024] In scenario 2, in one possible implementation, the MAC subheader of the MAC sub-PDU used for fallback includes the first time domain indication field; the first time domain indication field is used to indicate second time domain information. Therefore, in scenario 2, by configuring the first time domain indication field in the MAC subheader of the MAC sub-PDU used for fallback, the network device enables the UE to perform a judgment based on the time domain information indicated by the first time domain indication field to obtain a judgment result on whether the MAC sub-PDU used for fallback is related to itself.

[0025] Optionally, when the multiple UEs send the first message using an orthogonal coverage code (OCC) sequence, the MAC subheader of the MAC sub-PDU used for fallback further includes the first OCC indication field. The first OCC indication field indicates a fourth OCC sequence, which represents the OCC sequence used by the UE performing the fallback operation among the multiple UEs sending the first message at different time-domain locations. Therefore, in scenarios applying OCC, the network device configures the first time-domain indication field and the first OCC indication field in the MAC subheader of the MAC sub-PDU used for fallback, enabling the UE to perform a joint judgment based on the time-domain information indicated by the first time-domain indication field and the OCC sequence indicated by the first OCC indication field, to obtain a judgment result regarding whether the MAC sub-PDU used for fallback is related to itself.

[0026] In scenario 3, in some embodiments, the network device receives first messages sent by multiple UEs at the same frequency and time domain locations. The one or more MAC sub-PDUs carrying the contention result include a third MAC sub-PDU. The MAC header of the third MAC sub-PDU includes the second OCC indication field and / or the length indication field. The second OCC indication field indicates a fifth OCC sequence, which represents the OCC sequence corresponding to the UE associated with the fifth MAC sub-PDU among the multiple UEs sending the first message at the same frequency and time domain locations, or the OCC sequence corresponding to the UE that successfully competed for the contention. Therefore, in scenario 3, by configuring the second OCC indication field and / or the length indication field in the MAC header of the third MAC sub-PDU, the network device enables the UE to perform a judgment based on the OCC sequence indicated by the second OCC indication field to obtain a judgment result on whether the third MAC sub-PDU is related to itself. Furthermore, if the third MAC sub-PDU is determined to be irrelevant, the network device can skip data decoding of the corresponding length based on the length indication field, which helps improve decoding efficiency.

[0027] Optionally, the MAC subheader of the MAC sub-PDU for rollback includes the first OCC indication field; the first OCC indication field is used to indicate a sixth OCC sequence, which represents the OCC sequence used by the UE performing the rollback operation. Therefore, in case 3, by configuring the first OCC indication field in the MAC subheader of the MAC sub-PDU for rollback, the network device enables the UE to perform a judgment based on the OCC sequence indicated by the first OCC indication field to obtain a judgment result on whether the MAC sub-PDU for rollback is related to itself.

[0028] Before applying the aforementioned second message, the network device can configure multiple UEs to reuse the relevant information of the second message. Optionally, in one possible implementation, before receiving the first message sent by multiple UEs, the method further includes: the network device sending a system message, the system message being used to configure the relevant information of the second message reused for the multiple UEs.

[0029] In one possible implementation, the system message includes one or more of the following:

[0030] Enable the information in the second message;

[0031] Information on the capability to support the second message;

[0032] The preset conditions for the UE to use the second message as a response to the first message;

[0033] Maximum number of attempts, which refers to the maximum number of times the UE sends the first message and the application responds with the second message;

[0034] The multiplexing method of the second message includes one or more of the following: multiplexing of the second message when multiple UEs send the first message based on the same time domain location; multiplexing of the second message when multiple UEs send the first message based on the same frequency domain location; multiplexing of the second message when multiple UEs send the first message based on the same time and frequency domain location.

[0035] In one possible implementation, for case 1, the system message further includes one or more of the following: frequency domain information of the network device sending the second message; when the second message is used as a response to the first message, a set of frequency domains that can be used to send the first message and frequency domain location information of the network device sending the second message in the set of frequency domains.

[0036] Furthermore, after receiving or reading the second message, the UE can send a feedback message to the network device. The feedback message is a response to the second message. The network device can configure resources for the UE to transmit the feedback message. In one possible implementation, for case 1, the method further includes: the network device sending first indication information, which indicates HARQ resources for the feedback of the second message. The first indication information is carried in any of the following signaling: a system message, a downlink control information (DCI), a MAC SDU in the second message, a contention-based MAC sub-PDU in the second message, or a padding field in the second message. Therefore, the network device can configure resources for transmitting HARQ in various ways, enabling the UE to use the corresponding resources to transmit HARQ, providing a relatively flexible implementation.

[0037] In one possible implementation, for scenario 2 or 3, the method further includes: the network device sending second indication information, the second indication information indicating HARQ resources for the feedback of the second message, the first indication information being carried in downstream control information (DCI). Therefore, by configuring resources for transmitting HARQ, the network device enables the UE to use the corresponding resources to transmit HARQ.

[0038] Secondly, a method for data transmission is provided. This method can be executed by a first user equipment (UE), or by a component (such as a circuit, chip, or chip system) configured in the first UE, or by a logic module or software capable of implementing all or part of the functions of the first UE. This application does not limit this method.

[0039] Specifically, the method includes: a first UE sending a first message (e.g., CB MSG3), the first message being used to transmit uplink data; and receiving a second message from a network device (e.g., a MAC message or MSG4), the second message containing contention result information notifying multiple UEs, including the first UE. Based on the above technical solution, by receiving the multiplexed second message, compared to the network device sending a response to the first message for each UE, this embodiment of the application multiplexes the responses of multiple first messages into a single message (e.g., the second message), which can significantly improve transmission efficiency.

[0040] Furthermore, in this embodiment of the application, the frequency domain indicator field and / or time domain indicator field are carried in the sub-header of the message body, so that the UE can quickly know whether a certain information included in the second message is information about the competition result against itself, which can improve decoding efficiency.

[0041] In one possible implementation, the second message is a MAC PDU; the MAC PDU includes one or more of the following:

[0042] The MAC sub-PDU for rollback includes one or more of the following indication fields in its MAC sub-header: a first frequency domain indication field, a first time domain indication field, and a first orthogonal coverage code (OCC) indication field; the first frequency domain indication field indicates the frequency domain information corresponding to the UE performing the rollback operation among the plurality of UEs; the first time domain indication field indicates the time domain information corresponding to the UE performing the rollback operation among the plurality of UEs; and the first OCC indication field indicates the OCC sequence used by the UE performing the rollback operation among the plurality of UEs.

[0043] One or more MAC sub-PDUs are used to carry the contention result, wherein the MAC subheader of each MAC sub-PDU includes one or more of the following: a second frequency domain indication field, a second time domain indication field, a length indication field, and a second OCC indication field; the second frequency domain indication field is used to indicate the frequency domain information corresponding to the UE that successfully competed, or the frequency domain information corresponding to the UE related to the contention result; the second time domain indication field is used to indicate the time domain information corresponding to the UE that successfully competed, or the time domain information corresponding to the UE related to the contention result; the length indication field is used to indicate the length information of the data decoding that the UE needs to skip; the second OCC indication field is used to indicate the OCC sequence adopted by the UE that successfully competed, or the OCC sequence adopted by the UE related to the contention result;

[0044] The MAC sub-PDU for backoff includes one or more of the following indication fields in its MAC sub-header: a third frequency domain indication field, a third time domain indication field, and a third OCC indication field; the third frequency domain indication field indicates the frequency domain information corresponding to the UE performing the backoff operation among the plurality of UEs; the third time domain indication field indicates the time domain information corresponding to the UE performing the backoff operation among the plurality of UEs; and the third OCC indication field indicates the OCC sequence adopted by the UE performing the backoff operation among the plurality of UEs.

[0045] One or more MAC SDUs and / or MAC CEs are associated with the one or more MAC sub-PDUs used to carry the competition results.

[0046] There are three scenarios for sending the first message at the same time domain location and / or the same frequency domain location. Correspondingly, there are also corresponding implementation methods for multiplexing the second message in each scenario. These will be described separately below.

[0047] Scenario 1: In some embodiments, the one or more MAC sub-PDUs used to carry the contention result include a first MAC sub-PDU, the MAC sub-header of the first MAC sub-PDU including the second frequency domain indication field and / or the length indication field; the second frequency domain indication field is used to indicate the first frequency domain information; the method further includes:

[0048] If the frequency domain position corresponding to the first frequency domain information is the same as the first frequency domain position, the UE determines that the first MAC sub-PDU is related to the first UE, or determines to decode the first MAC sub-PDU, wherein the first frequency domain position is the frequency domain position where the first UE sends the first message;

[0049] If the frequency domain position corresponding to the first frequency domain information is different from the first frequency domain position, skip the decoding of the first MAC sub-PDU, or skip the data decoding of the first length, where the first length is determined based on the length indication field.

[0050] Therefore, in Case 1, the UE performs a judgment based on the frequency domain information indicated by the second frequency domain indication field of the network device to obtain a judgment result on whether the first MAC sub-PDU is related to itself; and, if it is determined that the first MAC sub-PDU is not related, it can also skip the data decoding of the corresponding length based on the length indication field, which helps to improve decoding efficiency.

[0051] Optionally, the MAC subheader of the first MAC subPDU further includes a second OCC indication field, which is used to indicate a first OCC sequence; the method further includes: determining that the first MAC subPDU is related to the first UE when the frequency domain position corresponding to the first frequency domain information is the same as the first frequency domain position, and the OCC sequence used by the first UE to send the first message is the same as the first OCC sequence, or determining to decode the first MAC subPDU;

[0052] If the frequency domain position corresponding to the first frequency domain information is different from the first frequency domain position, and / or the OCC sequence used by the first UE to send the first message is different from the first OCC sequence, it is determined that the first MAC sub-PDU is not related to the first UE, or it is determined that the first MAC sub-PDU is not decoded, or it is determined that the decoding of the first MAC sub-PDU is skipped, or it is determined that the data decoding of the first length is skipped, wherein the first length is determined based on the length indication field.

[0053] Therefore, in scenarios where OCC is applied, the UE performs a joint judgment based on the frequency domain information indicated by the second frequency domain indication field configured by the network device and the OCC sequence indicated by the second OCC indication field, in order to determine whether the first MAC sub-PDU is related to itself.

[0054] Optionally, the first MAC sub-PDU includes a contention success RAR; or, the first MAC sub-PDU is a contention resolution MAC CE.

[0055] For scenario 1, in one possible implementation, the MAC sub-header of the MAC sub-PDU for rollback includes the first frequency domain indication field, which indicates second frequency domain information; the method further includes:

[0056] If the frequency domain position corresponding to the second frequency domain information is the same as the first frequency domain position, a rollback operation is performed.

[0057] If the frequency domain position corresponding to the second frequency domain information is different from the first frequency domain position, it is determined that it is unrelated to the MAC sub-PDU used for rollback.

[0058] Therefore, the first UE can perform a judgment based on the frequency domain information indicated by the first frequency domain indication domain through the network device to obtain a judgment result on whether the MAC sub-PDU used for backoff is related to itself.

[0059] Optionally, the MAC sub-header of the MAC sub-PDU for rollback further includes the first OCC indication field; the first OCC indication field is used to indicate a second OCC sequence, the second OCC sequence representing the OCC sequence used by the UE performing the rollback operation; the method further includes:

[0060] If the frequency domain position corresponding to the second frequency domain information is the same as the first frequency domain position, and the OCC sequence used by the first UE to send the first message is the same as the second OCC sequence, then a rollback operation is performed.

[0061] If the frequency domain position corresponding to the second frequency domain information is different from the first frequency domain position, and / or the OCC sequence used by the first UE to send the first message is different from the second OCC sequence, it is determined that it is unrelated to the MAC sub-PDU used for backoff.

[0062] Therefore, in scenarios where OCC is applied, the UE can make a judgment based on the frequency domain information indicated by the first frequency domain indication field and the OCC sequence indicated by the first OCC indication field, in order to obtain a judgment result on whether the MAC sub-PDU used for backoff is related to itself.

[0063] Optionally, the MAC sub-PDU for rollback includes a rollback RAR; or, the MAC sub-PDU for rollback is a MAC CE for rollback.

[0064] Scenario 2: In some embodiments, the one or more MAC sub-PDUs used to carry the competition result include a second MAC sub-PDU, the MAC sub-header of the second MAC sub-PDU including the second time domain indication field and / or the length indication field; the second time domain indication field is used to indicate the first time domain information;

[0065] The method further includes:

[0066] If the time domain position corresponding to the first time domain information is the same as the first time domain position, it is determined that the second MAC sub-PDU is related to the first UE, or it is determined that the first MAC sub-PDU is decoded, wherein the first time domain position is the time domain position where the first UE sends the first message;

[0067] If the time domain position corresponding to the first time domain information is different from the first time domain position, skip the decoding of the second MAC sub-PDU, or skip the data decoding of the second length, which is determined based on the length indication field.

[0068] Therefore, in case 2, the UE can make a judgment based on the time domain information indicated by the second time domain indication field to obtain a judgment result on whether the second MAC sub-PDU is related to itself; and, if it is determined that the second MAC sub-PDU is not related, it can also skip the data decoding of the corresponding length based on the length indication field, which helps to improve decoding efficiency.

[0069] Optionally, when the multiple UEs transmit the first message at different time domain positions in the same frequency domain position using orthogonal coverage code (OCC) sequences, the subheader of the second MAC subPDU further includes a second OCC indication field; the second OCC indication field is used to indicate a third OCC sequence; the third OCC sequence represents the OCC sequence corresponding to the UE associated with the second MAC subPDU among the multiple UEs, or the OCC sequence corresponding to the UE that successfully competes among the multiple UEs.

[0070] The method further includes: determining that the second MAC sub-PDU is related to the first UE when the time domain position corresponding to the first time domain information is the same as the first time domain position, and the OCC sequence used by the first UE to send the first message is the same as the third OCC sequence; or determining to decode the second MAC sub-PDU.

[0071] If the time domain position corresponding to the first time domain information is different from the first time domain position, and / or the OCC sequence used by the first UE to send the first message is different from the third OCC sequence, it is determined that the second MAC sub-PDU is not related to the first UE, or the decoding of the second MAC sub-PDU is skipped, or the data decoding of the second length is skipped, the second length being determined based on the length indication field.

[0072] Therefore, in scenarios where OCC is applied, the UE can make a judgment based on the time domain information indicated by the second time domain indication field and the OCC sequence indicated by the second OCC indication field.

[0073] For scenario 2, in one possible implementation, the MAC sub-header of the MAC sub-PDU used for rollback includes a first time-domain indication field; the first time-domain indication field is used to indicate second time-domain information; the method further includes:

[0074] If the time domain position corresponding to the second time domain information is the same as the first time domain position, a rollback operation is performed; if the time domain position corresponding to the second time domain information is different from the first time domain position, it is determined that it is unrelated to the MAC sub-PDU used for rollback.

[0075] Therefore, in case 2, the UE can perform a judgment based on the time domain information indicated by the first time domain indication domain to obtain a judgment result on whether the MAC sub-PDU used for backoff is related to itself.

[0076] Optionally, when multiple UEs transmit the first message at different time-domain locations within the same frequency domain using orthogonal coverage code (OCC) sequences, the MAC sub-header of the MAC sub-PDU for rollback further includes the first OCC indication field; the first OCC indication field is used to indicate a fourth OCC sequence, which represents the OCC sequence used by the UE performing the rollback operation among the multiple UEs transmitting the first message at different time-domain locations; the method further includes: performing a rollback operation when the time-domain location corresponding to the second time-domain information is the same as the first time-domain location, and the OCC sequence used by the first UE to transmit the first message is the same as the fourth OCC sequence; and determining that it is unrelated to the MAC sub-PDU for rollback when the time-domain location corresponding to the second time-domain information is different from the first time-domain location, and / or the OCC sequence used by the first UE to transmit the first message is different from the fourth OCC sequence.

[0077] Therefore, in scenarios where OCC is applied, the UE can perform a joint judgment based on the time domain information indicated by the first time domain indication field and the OCC sequence indicated by the first OCC indication field to obtain a judgment result on whether the MAC sub-PDU used for backoff is related to itself.

[0078] Case 3: In some embodiments, the one or more MAC sub-PDUs used to carry the competition result include a third MAC sub-PDU, the MAC sub-header of which includes the second OCC indication field and / or the length indication field;

[0079] The second OCC indication field is used to indicate the fifth OCC sequence, which represents the OCC sequence corresponding to the UE associated with the third MAC sub-PDU among multiple UEs that send the first message at the same frequency domain position and the same time domain position, or the OCC sequence corresponding to the UE that successfully competes for the message; the method further includes:

[0080] If the OCC sequence used by the first UE to send the first message is the same as the fifth OCC sequence, it is determined that it is related to the third MAC sub-PDU, or it is determined that the third MAC sub-PDU is decoded;

[0081] If the OCC sequence used by the first UE to send the first message is different from the fifth OCC sequence, it is determined that it is unrelated to the third MAC sub-PDU, or it is determined that the third MAC sub-PDU will not be decoded, or the data decoding of the third length is skipped, the third length being determined based on the length indication field.

[0082] Therefore, in case 3, the UE can perform a judgment based on the OCC sequence indicated by the second OCC indication field to obtain a judgment result on whether the third MAC sub-PDU is related to itself; and, if it is determined that the third MAC sub-PDU is not related, it can also skip the data decoding of the corresponding length based on the length indication field, which helps to improve decoding efficiency.

[0083] Optionally, the MAC sub-header of the MAC sub-PDU used for rollback includes the first OCC indication field; the first OCC indication field is used to indicate a sixth OCC sequence, the sixth OCC sequence representing the OCC sequence used by the UE performing the rollback operation; the method further includes: performing a rollback operation if the OCC sequence used by the first UE to send the first message is the same as the sixth OCC sequence; and determining that it is unrelated to the MAC sub-PDU used for rollback if the OCC sequence used by the first UE to send the first message is different from the sixth OCC sequence. Therefore, in case 3, the UE can perform a judgment based on the OCC sequence indicated by the first OCC indication field through the network device to obtain a judgment result on whether the MAC sub-PDU used for rollback is related to itself.

[0084] Optionally, in one possible implementation, before the first UE sends the first message, the method further includes: the UE receiving a system message, the system message being used to configure multiple UEs to reuse relevant information of the second message.

[0085] In one possible implementation, the system message includes one or more of the following:

[0086] Enable the information in the second message;

[0087] Information on the capability to support the second message;

[0088] The preset conditions for the UE to use the second message as a response to the first message;

[0089] Maximum number of attempts, which refers to the maximum number of times the UE can send the first message and the application can respond with the second message;

[0090] The multiplexing method of the second message includes one or more of the following: multiplexing of the second message when multiple UEs send the first message based on the same time domain location; multiplexing of the second message when multiple UEs send the first message based on the same frequency domain location; multiplexing of the second message when multiple UEs send the first message based on the same time and frequency domain location.

[0091] In one possible implementation, for case 1, the system message further includes one or more of the following: frequency domain information of the network device sending the second message; when the second message is used as a response to the first message, a set of frequency domains that can be used to send the first message and frequency domain information of the network device sending the second message in the set of frequency domains; wherein, the first UE receiving the second message from the network device includes: receiving the second message according to the frequency domain information of the second message.

[0092] Furthermore, after receiving or reading the second message, the UE can send a feedback message to the network device. The feedback message is a response to the second message. The network device can configure resources for the UE to transmit the feedback message. In one possible implementation, for case 1, the first UE receives first indication information, which indicates the HARQ resources for the feedback of the second message. The first indication information is carried in any of the following signaling: a system message, a downlink control information (DCI), a MAC SDU in the second message, a contention-based MAC sub-PDU in the second message, or a padding field of the second message; based on the first indication information, the UE determines the HARQ resources for the feedback of the second message and transmits HARQ based on the HARQ resources.

[0093] In one possible implementation, for case 2 or case 3, the method further includes: a first UE receiving second indication information, the second indication information being used to indicate HARQ resources for the second message feedback, the first indication information being carried in line control information (DCI); determining HARQ resources for the second message feedback based on the second indication information, and transmitting HARQ based on the HARQ resources.

[0094] It should be noted that the second aspect is the UE-side implementation corresponding to the first aspect. The explanations (such as the explanation of terminology, description of specific implementation methods), supplements, and descriptions of beneficial effects of the first aspect also apply to the second aspect. For the sake of brevity, the various specific implementation methods will not be elaborated on in the second aspect.

[0095] Thirdly, a communication apparatus is provided, comprising modules or units for performing the method in any possible implementation of the first aspect described above.

[0096] In one design, the communication device may include modules that perform the methods / operations / steps / actions described in the foregoing aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0097] In one design, the communication device is a communication chip, which may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0098] In another design, the communication device is a communication equipment, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0099] In another design, the communication device is used to perform the method in any possible implementation of the first aspect described above. The communication device may be configured in the network device described above, or the communication device itself may be a network device.

[0100] Alternatively, the network equipment may be access network equipment (eNB or gNB), core network equipment, or a satellite.

[0101] Fourthly, a communication apparatus is provided, comprising modules or units for performing the method in any possible implementation of the second aspect described above.

[0102] In one design, the communication device may include modules that perform the methods / operations / steps / actions described in the foregoing aspects. These modules may be hardware circuits, software, or a combination of hardware circuits and software.

[0103] In one design, the communication device is a communication chip, which may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0104] In another design, the communication device is a communication equipment, which may include a transmitter for sending information or data and a receiver for receiving information or data.

[0105] In another design, the communication device is used to perform the method in any possible implementation of the second aspect described above. The communication device may be configured in the UE, or the communication device itself may be the UE.

[0106] Fifthly, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the first aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0107] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0108] In another implementation, the communication device is a chip configured in a network device. When the communication device is a chip configured in a network device, the communication interface can be an input / output interface.

[0109] In a sixth aspect, a communication device is provided, including a processor. The processor is coupled to a memory and can be used to execute instructions or data in the memory to implement the method in any possible implementation of the second aspect described above. Optionally, the communication device further includes a memory. Optionally, the communication device further includes a communication interface, and the processor is coupled to the communication interface.

[0110] In one implementation, the communication interface may be a transceiver, or an input / output interface.

[0111] In another implementation, the communication device is a chip configured in the UE. When the communication device is a chip configured in the UE, the communication interface can be an input / output interface.

[0112] In a seventh aspect, a processor is provided, comprising: an input circuit, an output circuit, and a processing circuit. The processing circuit is configured to receive signals through the input circuit and transmit signals through the output circuit, causing the processor to execute a method in any possible implementation of any aspect.

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

[0114] Eighthly, a communication device is provided, including a processor and a memory. The processor is used to read instructions stored in the memory, receive signals via a receiver, and transmit signals via a transmitter to execute the method in any possible implementation of any of the preceding aspects.

[0115] Optionally, the processor may be one or more, and the memory may be one or more.

[0116] Optionally, the memory may be integrated with the processor, or the memory may be separated from the processor.

[0117] In specific implementation, the memory can be a non-transitory memory, such as read-only memory (ROM), which can be integrated with the processor on the same chip or set on different chips. The embodiments of this application do not limit the type of memory or the way the memory and processor are set.

[0118] It should be understood that the relevant data interaction process, such as sending indication information, can be the process of the processor outputting indication information, and receiving capability information can be the process of the processor receiving input capability information. Specifically, the data output by the processor can be sent to the transmitter, and the input data received by the processor can come from the receiver. Here, the transmitter and receiver can be collectively referred to as a transceiver.

[0119] The processing device mentioned in the eighth aspect above can be one or more chips. The processor in the processing device can be implemented in hardware or software. When implemented in hardware, the processor can be a logic circuit, integrated circuit, etc.; when implemented in software, the processor can be a general-purpose processor that reads software code stored in memory. The memory can be integrated into the processor or located outside the processor and exist independently.

[0120] Ninthly, a computer program product is provided, the computer program product comprising: a computer program (also referred to as code or instructions), which, when the computer program is run, causes a computer to perform a method in any possible implementation of any of the above aspects.

[0121] In a tenth aspect, a computer-readable storage medium is provided that stores 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.

[0122] Eleventhly, embodiments of this application provide 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.

[0123] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0124] In a twelfth aspect, a communication system is provided, including a plurality of UEs (at least including the aforementioned first UE) and a network device. Optionally, the communication system may further include other devices that communicate with the UEs and / or the network device. Attached Figure Description

[0125] Figure 1 is an example diagram of a communication system;

[0126] Figure 2 is an example diagram of an access network device;

[0127] Figure 3 is an example interactive diagram of a data transmission method according to an embodiment of this application;

[0128] Figures 4A and 4B are example diagrams of different message body structures of the MAC PDU designed in the embodiments of this application;

[0129] Figures 5A to 5D are example diagrams of message body structures for different MAC subheaders of MAC sub-PDUs designed for carrying race results in case 1 according to embodiments of this application;

[0130] Figures 6A to 6D are example diagrams of the message body structure of different MAC subheaders of the MAC sub-PDU for rollback designed for situation 1 in the embodiments of this application;

[0131] Figures 6E to 6H are example diagrams of the message body structure of different MAC subheaders of the MAC sub-PDU designed for backoff in the embodiments of this application for case 1;

[0132] Figures 7A to 7D are example diagrams of message body structures for different MAC subheaders of MAC sub-PDUs designed for carrying race results in case 2 according to embodiments of this application;

[0133] Figures 8A to 8D are example diagrams of the message body structure of different MAC subheaders of the MAC sub-PDU for rollback designed according to the embodiments of this application for situation 2;

[0134] Figures 8E to 8H are example diagrams of the message body structure of different MAC subheaders of the MAC sub-PDU for backoff designed according to the embodiments of this application for situation 2;

[0135] Figures 9A and 9B are example diagrams of message body structures for different MAC sub-headers of MAC sub-PDUs designed for carrying competition results in case 3 according to embodiments of this application;

[0136] Figures 10A and 10B are example diagrams of the message body structure of different MAC subheaders of the MAC sub-PDU for rollback designed for situation 3 in the embodiments of this application;

[0137] Figures 10C to 10D are example diagrams of the message body structure of different MAC subheaders of the MAC sub-PDU for backoff designed according to the embodiments of this application for situation 3;

[0138] Figure 11 is an example diagram of the frequency domain location of the network device configuration acquisition message 4 according to an embodiment of this application;

[0139] Figure 12 is a schematic block diagram of a communication device provided in an embodiment of this application;

[0140] Figure 13 is another schematic block diagram of the communication device provided in the embodiments of this application. Detailed Implementation

[0141] The technical solutions in the embodiments of this application will now be described with reference to the accompanying drawings.

[0142] In this application embodiment, "multiple" can be understood as "at least two"; "multiple items" can be understood as "at least two items".

[0143] This application can be applied to communication systems. Mobile communication systems include, but are not limited to, the following systems: Long Term Evolution (LTE) systems, Universal Mobile Telecommunication System (UMTS), Worldwide Interoperability for Microwave Access (WiMAX) systems, 5th Generation (5G) systems or new radio (NR) systems and future mobile communication systems, vehicle-to-X (V2X) systems, where V2X can include vehicle-to-network (V2N), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), vehicle-to-pedestrian (V2P), etc., Long Term Evolution-Vehicle (LTE-V) technology for vehicle-to-everything (V2X), vehicle-to-everything (V2X), machine-type communication (MTC), Internet of Things (IoT), Long Term Evolution-Machine (LTE-M) technology for machine-to-machine (M2M), etc. The 5G mobile communication system may include non-standalone (NSA) and / or standalone (SA) networking. The technical solutions provided in this application can also be applied to future communication systems. This application does not limit the scope of the application.

[0144] This application can also be applied to systems that integrate satellite and communication systems, such as NTN systems.

[0145] In some embodiments, this application can be applied to non-terrestrial network (NTN) systems such as satellite communication systems and high altitude platform station (HAPS) communication, for example, global navigation satellite systems (GNSS). Satellite communication systems include geostationary earth orbit (GEO) satellites and non-geostationary earth orbit (NGEO) satellites.

[0146] A geostationary satellite is a service satellite that is stationary relative to a fixed point on the Earth's surface. In other words, within the same service area, the satellite is stationary. A geostationary satellite can be understood as a geostationary satellite. A geostationary satellite is a satellite operating in a geostationary orbit, and can also be simply called a geostationary satellite. For geostationary satellites, the relative motion between the geostationary satellite and the user (UE) is mainly caused by changes in the UE's position.

[0147] Non-geostationary orbit satellites can include various types of satellites other than those in geostationary orbit. Non-geostationary orbit satellites operate in non-geostationary orbits and are in motion relative to a fixed point on the Earth's surface. Their orbital speed is not synchronized with the Earth's rotation. For non-geostationary orbit satellites, the relative motion between the satellite and the UE (Unified Component Object) is primarily caused by the motion of the non-geostationary orbit satellite itself.

[0148] In some embodiments, the present application is applicable to non-synchronous orbit satellite communication systems.

[0149] It is understandable that satellite communication systems can be integrated with traditional mobile communication systems to provide communication services.

[0150] Figure 1 is a schematic diagram of the architecture of a mobile communication system 1000 applicable to an embodiment of this application. As shown in Figure 1, the communication system 1000 includes a radio access network 100 and a core network 200. Optionally, the communication system 1000 also includes an Internet 300. Optionally, the Internet 300 can be connected to the radio access network 100 or the core network 200 wirelessly or via a wired connection. The radio access network 100 may include at least one access network device (110a and 110b in Figure 1, collectively referred to as 110), and may also include at least one terminal (120a-120k in Figure 1, collectively referred to as 120). Terminals 120a-120k are wirelessly connected to access network devices 110a and 110b. Access network devices 110a and 110b are wirelessly or via a wired connection to the core network 200. The core network device in the core network and the access network device in the radio access network may be different physical devices, or they may be the same physical device integrating core network logical functions and radio access network logical functions. Terminals can connect to each other wirelessly. Access network devices can connect to each other via wired or wireless means. Figure 1 is only a schematic diagram; the communication system may also include other network devices, such as wireless relay devices and / or wireless backhaul devices (not shown in Figure 1). The communication system may, for example, support 3GPP-related cellular systems (e.g., 5G communication systems, communication systems integrating multiple wireless technologies (e.g., communication systems integrating at least two of 2G, 3G, 4G, or 5G technologies), or future-oriented evolution systems), or wireless fidelity (WiFi) systems, or 3GPP-related cellular systems integrating other technologies, or future communication systems, etc.

[0151] It should be understood that the communication links of the various devices in the mobile communication system 1000 shown in Figure 1 are merely illustrative examples, and the embodiments of this application are not limited thereto. Taking the XR device 120k as an example, the XR device can communicate with a terminal device, or it can communicate with an access network device.

[0152] The network devices in this application embodiment can be network-side devices such as access network devices and core network devices. Access network devices are sometimes also called access nodes. Access network devices have wireless transceiver capabilities for communicating with terminals. Access network devices include, but are not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs) in the aforementioned communication systems, next-generation NodeBs (gNBs) in 5G mobile communication systems, access network devices or modules of access network devices in Open RAN (ORAN) systems, base stations in future mobile communication systems, or access nodes in WiFi systems. Access network devices can also be modules or units capable of implementing some of the functions of a base station. For example, access network devices can be the central unit (CU), distributed unit (DU), CU-control plane (CP), CU-user plane (UP), or radio unit (RU) described below. In the ORAN system, CU can also be called O-CU, DU can also be called open (O)-DU, CU-CP can also be called O-CU-CP, CU-UP can also be called O-CUP-UP, and RU can also be called O-RU. The access network equipment can be a macro base station (as shown in Figure 1, 110a), a micro base station or indoor station (as shown in Figure 1, 110b), a relay node or donor node, or a wireless controller in a cloud radio access network (CRAN) scenario. Optionally, the access network equipment can also be a server, wearable device, or vehicle-mounted equipment, etc. For example, the access network equipment in vehicle-to-everything (V2X) technology can be a roadside unit (RSU). Multiple access network equipment in the communication system can be base stations of the same type or different types. Base stations can communicate with terminals or through relay stations. Terminals can communicate with multiple base stations in different access technologies. The embodiments of this application do not limit the specific technology or specific equipment form used in the access network equipment. In this application, the access network device is referred to as a network device.

[0153] The terminal device in this application can be a wireless terminal device capable of receiving network device scheduling and instruction information. The wireless terminal device can be a device providing voice and / or data connectivity to a user, a handheld device with wireless connectivity, or other processing devices connected to a wireless modem. For example, the terminal device can communicate with one or more core networks or the Internet via a radio access network (RAN). The terminal device can also be referred to as a terminal, user equipment (UE), mobile station, mobile terminal, etc. Terminal devices can be widely used in various scenarios, such as device-to-device (D2D), vehicle-to-everything (V2X) communication, machine-type communication (MTC), Internet of Things (IoT), ultra-reliable low-latency communication (URLLC), virtual reality, augmented reality, industrial control, autonomous driving, telemedicine, smart grids, smart furniture, smart offices, smart wearables, smart transportation, smart cities, or satellite communication, etc. The terminal can be a mobile phone, tablet computer, computer with wireless transceiver capabilities, wearable device, vehicle, aircraft (such as drone, helicopter, airplane), hot air balloon, ship, robot, robotic arm, or smart home device, etc. The embodiments of this application do not limit the form of the terminal device.

[0154] By way of example and not limitation, in this embodiment, the UE can also be a wearable device. Wearable devices, also known as wearable smart devices, are a general term for devices that utilize wearable technology to intelligently design and develop everyday wearables, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices worn directly on the body or integrated into a user's clothing or accessories. Wearable devices are not merely hardware devices; they achieve powerful functions through software support, data interaction, and cloud interaction. Broadly defined, wearable smart devices include those with comprehensive functions, large size, and the ability to perform complete or partial functions without relying on a smartphone, such as smartwatches or smart glasses, as well as those focused on a specific application function that require interaction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0155] Furthermore, in this embodiment, the UE can also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of future information technology development, and its main technical feature is connecting objects to networks through communication technologies, thereby realizing an intelligent network of human-machine interconnection and object-to-object interconnection. The embodiments of this application do not limit the specific technologies or device forms used in the terminal devices.

[0156] In this embodiment, the UE may include a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the structure of the execution entity of the method provided in this embodiment, as long as it can communicate according to the method provided in this embodiment by running a program that records the code of the method provided in this embodiment. For example, the execution entity of the method provided in this embodiment can be a terminal device, or a functional module in the terminal device that can call and execute a program.

[0157] Access network devices and / or terminals can be fixed or mobile. They can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; on water; or in the air on aircraft, balloons, and satellites. This application does not limit the application scenarios of the access network devices and terminals. Access network devices and terminal devices can be deployed in the same or different scenarios; for example, both can be deployed on land; or the access network device can be deployed on land, and the terminal device on water, etc., and so on.

[0158] In this embodiment, each element in the communication system can be considered a network element in the communication system. For example, the helicopter or drone 120i in Figure 1 can be configured as a mobile access network device. For terminal devices 120j that access the wireless access network 100 via 120i, the helicopter or drone 120i is an access network device; however, for access network device 110a, 120i is a terminal device, meaning that 110a and 120i communicate via a wireless air interface protocol. Alternatively, 110a and 120i can communicate via an interface protocol between access network devices. In this case, relative to 110a, 120i is also an access network device. Therefore, both access network devices and terminal devices can be collectively referred to as communication devices. 110a and 110b in Figure 1 can be called communication devices with access network device functions, and 120a-120k in Figure 1 can be called communication devices with terminal device functions.

[0159] In this application, the apparatus for implementing the functions of a network device can be the network device itself, or an apparatus capable of supporting the network device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the network device. Alternatively, the apparatus for implementing the functions of a network device can also be a control subsystem containing network device functions. For example, a control subsystem containing access network device functions can be a control center in scenarios where terminals can be applied, such as smart grids, industrial control, intelligent transportation, or smart cities. In the technical solutions provided in this application, the example of a network device being used to implement the functions of a network device is used to describe the technical solutions provided in this application.

[0160] In this application, the apparatus for implementing the functions of a terminal device can be the terminal device itself, or any apparatus capable of supporting the terminal device in implementing those functions, such as a processor, circuit, chip, or chip system. This apparatus can be installed in or connected to the terminal device. In the technical solution provided in this application, the UE (User Equipment) is used as an example to illustrate the technical solution provided in this application.

[0161] Communication between access network devices and terminal devices can follow a specific protocol layer structure. For example, this protocol layer structure may include a control plane protocol layer structure and a user plane protocol layer structure. For instance, the control plane protocol layer structure may include at least one of the following: radio resource control (RRC) layer, packet data convergence protocol (PDCP) layer, radio link control (RLC) layer, media access control (MAC) layer, or physical (PHY) layer. Similarly, the user plane protocol layer structure may include at least one of the following: service data adaptation protocol (SDAP) layer, PDCP layer, RLC layer, MAC layer, or physical layer.

[0162] As shown in Figure 2, the access network equipment may include a CU and a DU. This design can be referred to as CU and DU separation. Multiple DUs can be centrally controlled by a single CU. As an example, the interface between the CU and DU is called the F1 interface. The control plane (CP) interface can be F1-C, and the user plane (UP) interface can be F1-U. This application does not limit the specific names of each interface. The CU and DU can be divided 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) are set in the CU, and the functions of the protocol layers below the PDCP layer (e.g., RLC layer, MAC layer and PHY layer) are set in the DU; or, for 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.

[0163] The above division of CU and DU processing functions according to protocol layers is merely an example; other methods can also be used. For instance, CUs or DUs can be divided into those with more protocol layer functions, or they can be divided into those with partial protocol layer processing functions. For example, some functions of the RLC layer and the protocol layer functions above the RLC layer can be placed in the CU, while the remaining functions of the RLC layer and the protocol layer functions below the RLC layer can be placed in the DU. Furthermore, the functions of CUs or DUs can be divided according to service type or other system requirements, such as by latency. Functions that need to meet latency requirements can be placed in the DU, while functions that do not need to meet this latency requirement can be placed in the CU.

[0164] Optionally, the CU may have one or more core network functions.

[0165] Optionally, the radio unit (RU) of the DU can be remotely located. The RU has radio frequency (RF) functionality. For example, the DU and RU can be separated at the PHY layer. For instance, the DU can implement higher-level functions in the PHY layer, and the RU can implement lower-level functions. When transmitting, the PHY layer functions may include at least one of the following: adding cyclic redundancy check (CRC) bits, channel coding, rate matching, scrambling, modulation, layer mapping, precoding, resource mapping, physical antenna mapping, or RF transmission functionality. When receiving, the PHY layer functions may include at least one of the following: CRC check, channel decoding, rate matching de-scrambling, demodulation, layer mapping de-mapping, channel detection, resource demapping, physical antenna demapping, or RF reception functionality. The higher-level functions in the PHY layer may include a portion of the PHY layer's functionality, which is closer to the MAC layer; the lower-level functions in the PHY layer may include another portion of the PHY layer's functionality, for example, a portion closer to the RF functionality. For example, higher-level functions in the PHY layer may include adding CRC bits, channel coding, rate matching, scrambling, modulation, and layer mapping, while lower-level functions may include precoding, resource mapping, physical antenna mapping, and RF transmission functions; or, higher-level functions in the PHY layer may include adding CRC bits, channel coding, rate matching, scrambling, modulation, layer mapping, and precoding, while lower-level functions may include resource mapping, physical antenna mapping, and RF transmission functions. For example, higher-level functions in the PHY layer may include CRC checksum, channel decoding, rate matching de-matching, decoding, demodulation, and layer mapping de-matching, while lower-level functions may include channel detection, resource de-mapping, physical antenna de-mapping, and RF reception functions; or, higher-level functions in the PHY layer may include CRC checksum, channel decoding, rate matching de-matching, decoding, demodulation, layer mapping de-matching, and channel detection, while lower-level functions may include resource de-mapping, physical antenna de-mapping, and RF reception functions.

[0166] Optionally, the functions of the CU can be further divided, separating the control plane and the user plane and implementing them through different entities. The separated entities are the control plane CU entity (i.e., the CU-CP entity) and the user plane CU entity (i.e., the CU-UP entity). The CU-CP entity and the CU-UP entity can be connected to the DU respectively. In the embodiments of this application, an entity can be understood as a module or unit, and its form can be a hardware structure, a software module, or a hardware structure plus a software module, without limitation.

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

[0168] Currently, network devices configure shared resources for multiple UEs. If multiple UEs choose the same resources to transmit RRC messages and for uplink data transmission, conflicts will occur. Network devices resolve these conflicts by sending response messages (e.g., MAC PDU messages) to the UEs. However, sending a separate response message for each UE would impact transmission efficiency. Currently, the standard protocol has not yet provided a clear conclusion on how to reuse response messages.

[0169] In view of this, embodiments of this application provide a communication method in which a network device receives a first message sent by multiple UEs at the same time domain location and / or the same frequency domain location, the first message being used to transmit uplink data; and sends a second message to the multiple UEs, the second message including information on the contention result of the multiple UEs, i.e., reusing the second message helps to improve transmission efficiency.

[0170] The following detailed explanation of the solution provided in this application, in conjunction with the corresponding flowcharts, illustrates the method. It is understood that the illustrative flowcharts provided in this application primarily use different devices (e.g., UE or network devices) as examples of the execution entities for this interactive illustration, but this application does not limit the execution entities of the interactive illustrations. For example, the device (e.g., UE or network device) in the illustrative flowcharts can also be a chip, chip system, or processor that supports the implementation of this method on that device, or it can be a logic module or software capable of implementing all or part of the functions of that device.

[0171] As a general statement, the message or signaling interactions involved in the interaction process of this application embodiment can be standard messages or signaling or newly introduced messages or signaling. This application embodiment does not make specific limitations on this.

[0172] Figure 3 is an example interaction diagram for data transmission according to an embodiment of this application. It can be understood that the network device in Figure 3 can be the network device shown in Figure 1 or Figure 2, or it can refer to a device within the network device (e.g., a processor, chip, or chip system, etc.); any one of the N UEs in Figure 3 can be any terminal device in Figure 1, or it can refer to a device within the terminal device (e.g., a processor, chip, or chip system, etc.). N is an integer greater than or equal to 2. As shown in Figure 3, the method includes the following steps:

[0173] In step 310, multiple UEs (such as the N UEs shown in Figure 3) each send their own first message. Correspondingly, the network device receives multiple first messages.

[0174] In some embodiments, the network device receives a first message sent by multiple UEs at the same time domain location and / or the same frequency domain location. The first message is used to transmit uplink data. "Same time domain location and / or same frequency domain location" includes: the same time domain location but different frequency domain locations; or the same frequency domain location but different time domain locations; or the same time domain and frequency domain locations.

[0175] As a general statement, the embodiments of this application do not specifically limit the representation unit or granularity of the time domain position and / or frequency domain position, which may depend on the actual application or scenario.

[0176] For example, time-domain location can be characterized by one or more of the following: system frame number (SFN); radio frame number; hyperframe number (H-SFN); subframe index; time slot number; OFDM symbol; resource number in the resource window used to send the first message or a copy of the first message, etc.

[0177] For example, the resource number in the resource window used to send the first message or a copy of the first message is used to represent the Nth resource in the resource window used to send the first message or a copy of the first message.

[0178] For example, frequency domain location is characterized by one or more of the following: physical resource block index / identifier (PRB index / ID); carrier index; frequency point; frequency domain identifier.

[0179] This application does not specifically limit the message type and / or naming of the first message in its embodiments. In some embodiments, the first message is an RRC message. For example, the first message is the first RRC message in a newly introduced random access transport mechanism, or the first message is message 3 (MSG3) in a traditional random access transport mechanism, or the first message is message 3 in a newly introduced transport mechanism, or the first message is contention-based message 3 (CB MSG3). The newly introduced random access transport mechanism does not include a random access preamble and RAR. The first RRC message or message 3 can be an RRCEarlyDataRequest, RRCResumeRequest, or RRCConnectionRequest message, or a newly introduced / named RRC message. The traditional random access transport mechanism can be a four-step random access or an advance data transmission mechanism.

[0180] It should be noted that network devices can configure shared resources for multiple UEs, and multiple UEs can use these shared resources to send first messages, or in other words, send uplink data. For shared resources, multiple UEs may select the same resource, such as the same time-domain resource and / or the same frequency-domain resource. Therefore, the aforementioned multiple first messages can be first messages sent by multiple UEs at different frequency-domain locations within the same time-domain location; or, they can be first messages sent by multiple UEs at different time-domain locations within the same frequency-domain location; or, they can be first messages sent by multiple UEs at both the same time-domain location and the same frequency-domain location. Each UE can correspond to one first message; correspondingly, if there are multiple UEs, then there are multiple first messages.

[0181] In step 320, the network device sends a second message. Correspondingly, multiple UEs receive the second message. The second message includes contention result information (e.g., contention result information for random access) notifying the multiple UEs.

[0182] In one application scenario, the second message in step 320 includes notification of the competition results of multiple UEs. These multiple UEs can be several UEs out of N UEs, such as P UEs, where P is less than N.

[0183] Optionally, the N UEs include multiple competition groups, and each competition group includes multiple UEs that are in competition with each other. The second message sent by the network device in step 320 includes competition result information for the UEs that successfully competed in each competition group.

[0184] For example, consider N UEs belonging to the following three competition groups: the first competition group includes UE1 and UE2; the second competition group includes UE3 to UE5; and the third competition group includes UE6 to UE9. After UE1 to UE9 all send the first message, only some UEs will successfully compete. Assume the following UEs successfully compete: UE1 in the first competition group; UE4 in the second competition group; and UE6 in the third competition group. Then, the second message sent by the network device will include the competition result information for UE1, UE4, and UE6. These successfully competing UEs will receive the multiplexed second message sent by the network device, while the UEs that did not successfully compete will not receive the second message.

[0185] In another application scenario, UE1 to UE N can be free from competition. After receiving the first message from each of these N UEs, the network device can send the competition result information through a second message, that is, respond to the N UEs through message reuse. For example, if the number of multiple UEs in step 310 is N, and the number of multiple UEs mentioned in step 320 (i.e., the second message includes competition information notifying multiple UEs) is P, then N can be equal to P.

[0186] The second message in this embodiment is a multiplexing message, which means that the random access contention results for multiple UEs are sent to the UE in one message. For example, the second message is represented as multiplexing message 4 (multiplexing MSG4 / MSG4multiplexing).

[0187] Similarly, this application embodiment does not specifically limit the message type and / or naming of the second message. The second message is a response message to the first message. In some embodiments, the second message is a MAC layer message, such as a MAC PDU; or an RRC layer message. For example, the second message is MSG4 in the newly introduced transport mechanism, or the second message is message 4 (MSG4) in the traditional four-step random access transport mechanism or the advance data transmission (EDT) mechanism.

[0188] In some embodiments, multiple UEs can listen for and receive the second message through a public radio network temporary identifier (RNTI) or the same RNTI. This application does not specifically limit the type of RNTI. For example, the aforementioned public RNTI or the same RNTI can be a random access radio network temporary identifier (RA-RNTI); or it can be a newly introduced RNTI specifically used for listening to the second message in this application embodiment.

[0189] Optionally, the second message is sent as a MAC PDU. In other words, the second message is a MAC PDU message. The MAC PDU includes one or more of the following:

[0190] (1) A MAC sub-PDU for fallback, wherein the MAC sub-header of the MAC sub-PDU for fallback includes one or more of the following indication fields: a first frequency domain indication field, a first time domain indication field, and a first orthogonal coverage code (OCC) indication field; the first frequency domain indication field is used to indicate the frequency domain information (e.g., the frequency domain resource information used by the UE to send the first message) of the UE performing the fallback operation among the plurality of UEs; the first time domain indication field is used to indicate the time domain information (e.g., the time domain resource information used by the UE to send the first message) of the UE performing the fallback operation among the plurality of UEs; the first OCC indication field is used to indicate the OCC sequence (e.g., the OCC sequence used by the UE to send the first message) of the UE performing the fallback operation among the plurality of UEs.

[0191] (2) One or more MAC sub-PDUs for carrying contention results, wherein the MAC subheader of each MAC sub-PDU includes one or more of the following: a second frequency domain indication field, a second time domain indication field, a length indication field, and a second OCC indication field; the second frequency domain indication field is used to indicate the frequency domain information corresponding to the UE that successfully competed, or the frequency domain information corresponding to the UE related to the contention result (e.g., the frequency domain resource information used by the UE to send the first message); the second time domain indication field is used to indicate the time domain information corresponding to the UE that successfully competed (e.g., the time domain resource information used by the UE to send the first message), or the time domain information corresponding to the UE related to the contention result; the length indication field is used to indicate the length information of the data decoding that the UE needs to skip; the second OCC indication field is used to indicate the OCC sequence adopted by the UE that successfully competed, or the OCC sequence adopted by the UE related to the contention result (e.g., the OCC sequence used by the UE to send the first message);

[0192] (3) A MAC sub-PDU for backoff, wherein the MAC sub-header of the MAC sub-PDU for backoff includes one or more of the following indication fields: a third frequency domain indication field, a third time domain indication field, and a third OCC indication field; the third frequency domain indication field is used to indicate the frequency domain information (e.g., the frequency domain resource information used by the UE to send the first message) of the UE performing the backoff operation among the plurality of UEs; the third time domain indication field is used to indicate the time domain information (e.g., the time domain resource information used by the UE to send the first message) of the UE performing the backoff operation among the plurality of UEs; the third OCC indication field is used to indicate the OCC sequence adopted by the UE performing the backoff operation among the plurality of UEs (e.g., the OCC sequence used by the UE to send the first message);

[0193] (4) One or more MAC service data units (SDUs) and / or MAC CEs associated with the one or more MAC sub-PDUs used to carry the competition results.

[0194] It should be noted that the numbers (1) to (4) above are introduced only for ease of description and are not intended to limit the order or quantity.

[0195] In some embodiments, the MAC sub-PDU mentioned in (1) above can be understood or replaced as a MAC sub-PDU including a fallback RAR; or, it can be understood or replaced as a fallback MAC CE. Alternatively, the "MAC sub-PDU for fallback" mentioned in (1) above can be expressed or replaced as "response information for fallback", or replaced with other terms that have the same function or effect. Of course, the description of the "MAC sub-PDU for fallback" above can also be applied to the replaced terms. For ease of description, the embodiments of this application are described using "MAC sub-PDU for fallback" as an example. Optionally, the MAC sub-PDU for fallback includes a fallback RAR and a MAC sub-header. For example, by adding an indication field to the MAC sub-header in the "MAC sub-PDU for fallback", one or more of the following can be indicated: a UE that sends a first message at a specific time domain location performs a fallback operation; a UE that sends a first message at a specific frequency domain location performs a fallback operation; and a UE that uses a specific OCC sequence performs a fallback operation.

[0196] In some embodiments, the "one or more MAC sub-PDUs for carrying contention results" mentioned in (2) above can be understood or replaced with one or more contention RARs (e.g., success RARs); or, it can be understood or replaced with one or more MAC sub-PDUs for contention resolution; or it can be understood or replaced with one or more contention resolution MAC CEs. Alternatively, the "one or more MAC sub-PDUs for carrying contention results" mentioned in (2) above can be expressed or replaced with "one or more response information for carrying contention results"; or replaced with other terms that have the same function or effect. Of course, the description of "one or more MAC sub-PDUs for carrying contention results" above can also be applied to the replaced terms. For ease of description, the embodiments of this application use "one or more MAC sub-PDUs for carrying contention results" as an example. For example, by adding an indication field to the MAC subheader of any of the one or more MAC subPDUs used to carry the contention result, to indicate one or more of the following: UE contention success or contention resolution when sending the first message at a specific time domain location; UE contention success or contention resolution when sending the first message at a specific frequency domain location; and UE contention success or contention resolution when using a specific OCC sequence.

[0197] For clarity, the MAC sub-PDU used to carry the contention result includes information (or contention resolution identifier ID) in its entity portion (e.g., successRAR) related to contention resolution (or contention resolution result). If the UE uses the MAC sub-header of the MAC sub-PDU to carry the contention result, or if the MAC sub-PDU is related to itself, it can further decode the entity portion to obtain the contention resolution information. After obtaining this information, the UE can use it to perform further judgments to ultimately determine whether it has won the contention. For example, the UE checks whether the contention resolution identifier ID matches the identifier used in its uplink common control channel (CCCH) SDU for MSG3; if the identifier matches, the UE is determined to be the winning UE. For methods of determining identifier consistency, refer to descriptions in related technologies, such as those concerning contention mechanisms.

[0198] For example, the competition determines whether the first 48 bits of the identifier ID match the identifier used in the uplink CCCH SDU that it sends MSG3; if they match, the competition is considered won.

[0199] In some embodiments, the MAC SDU and / or MAC CE associated with the MAC sub-PDU for carrying the competition result mentioned in (4) above may include any one of the following: a MAC CE associated with the MAC sub-PDU for carrying the competition result; or a MAC SDU associated with the MAC sub-PDU for carrying the competition result; or a MAC CE and MAC SDU associated with the MAC sub-PDU for carrying the competition result.

[0200] Optionally, one of the MAC sub-PDUs carrying the contention result in (2) above may be associated with one of the MAC SDUs and / or MAC CEs in (4) above. A MAC sub-PDU carrying the contention result, and the associated MAC SDU and / or MAC CE, can be understood as a set of MAC sub-PDUs for a UE. The second message includes multiple sets of MAC sub-PDUs for multiple UEs. In other words, the second message may include multiple sets of MAC sub-PDUs, each set of MAC sub-PDUs corresponding to a UE, and each set of MAC sub-PDUs includes one MAC sub-PDU carrying the contention result; and one MAC SDU and / or MAC CE.

[0201] It should be noted that the above description of a MAC sub-PDU for carrying the competition result can be associated with a MAC SDU and / or MAC CE. However, the embodiments of this application do not limit whether the second message simultaneously includes: a MAC sub-PDU for carrying the competition result, and the associated MAC SDU and / or MAC CE. For example, the second message may include some or all of the MAC sub-PDUs for carrying the competition result, without the associated MAC SDU and / or MAC CE.

[0202] In some embodiments, the “MAC sub-PDU for backoff” mentioned in (3) above can be understood or replaced as a MAC sub-PDU that includes only a Backoff Indicator (BI) subheader, or expressed as a BI subheader (i.e., a MAC subheader with Backoff Indicator only). Alternatively, the “MAC sub-PDU for backoff” mentioned in (3) above can be expressed or replaced with other terms that have the same function or effect. Of course, the description of “MAC sub-PDU for backoff” above can also be applied to the replaced terms. For ease of description, the embodiments of this application are described using “MAC sub-PDU for backoff” as an example. For example, by adding an indication field to the MAC subheader of the MAC sub-PDU for backoff, one or more of the following can be indicated: a UE that sends a first message at a specific time domain location performs a backoff operation; a UE that sends a first message at a specific frequency domain location performs a backoff operation; and a UE that uses a specific OCC sequence performs a backoff operation.

[0203] In this context, backoff operation refers to the UE waiting for a certain period of time before initiating random access (e.g., sending the first message). In some embodiments, the MAC subheader of the MAC subPDU used for backoff includes a BI, which specifies the time range or duration that the UE needs to wait before sending the first message.

[0204] When the second message is sent in the form of a MAC PDU, the MAC PDU may include various types of MAC sub-PDUs. It should be understood that the content included in the second message shown above is merely an exemplary description, and the embodiments of this application are not limited thereto. In fact, the second message may also include other content. For example, the second message may also include one or more of the following: MAC sub-PDUs with other functions, and MAC sub-PDUs used for filling fields (including MAC subheader and padding).

[0205] For ease of understanding, the possible forms of the second message are described in conjunction with the message body structure shown in Figure 4A. As shown in Figure 4A, the MAC PDU message includes one or more of the following: a MAC sub-PDU carrying a backoff indication (BI) header, a MAC sub-PDU for backoff (such as the MAC sub-PDU including the backoff RAR in Figure 4A), and multiple sets of MAC sub-PDUs. Each set of MAC sub-PDUs may correspond to a contention resolution information (e.g., the contention resolution ID can be referred to the explanation in (2) above); or it may include a contention result information (refer to the description of contention resolution information in (2) above). Among them, each set of MAC sub-PDUs includes a MAC sub-PDU for contention (such as the successRAR in Figure 4A), or includes a MAC sub-PDU for contention and an associated MAC SDU.

[0206] That is, as shown by the dashed line in Figure 4A, the MAC SDU can also be optional (i.e., the MAC sub-PDU used for contention may not have an associated MAC SDU. For example, as shown in Figure 4A, each MAC sub-PDU used for contention includes a MAC sub-header and a successRAR, but does not include an associated MAC SDU. It should be understood that the embodiments of this application do not specifically limit the format of the MAC sub-header of the associated MAC SDU; the original sub-header can be used, or a newly defined sub-header can be used.

[0207] Alternatively, if the MAC PDU message shown in Figure 4A includes multiple MAC sub-PDUs for contention, some of these MAC sub-PDUs include an associated MAC SDU, while others do not include the associated MAC SDU.

[0208] Optionally, MAC PDU messages also include optional fields.

[0209] This application embodiment does not specifically limit the format of the BI subheader of the MAC sub-PDU carrying the rollback instruction in Figure 4A. For example, the content included in the BI subheader can follow the existing BI subheader format or it can be a newly defined format.

[0210] It should be understood that the embodiments of this application do not limit whether the MAC sub-PDU used for competition in Figure 4A is associated with a MAC SDU and / or MAC CE. For example, the MAC sub-PDU used for competition may be associated with a MAC CE, or it may be associated with both a MAC SDU and a MAC CE; or the MAC sub-PDU used for competition may not be associated with a MAC SDU or a MAC CE.

[0211] It should also be understood that the various MAC sub-PDUs involved in Figure 4A can be replaced with other representations, and the embodiments of this application do not specifically limit them. For example, the MAC sub-PDU used for rollback can also be replaced with response information (or response message) used for rollback. As another example, the MAC sub-PDU used for contention can also be replaced with one or more response information (or response message) used to carry the contention result.

[0212] In conjunction with the foregoing, by way of example, embodiments of this application may modify the MAC subheader of the MAC sub-PDU for rollback in FIG4A to include one or more of the following indication fields: a first frequency domain indication field, a first time domain indication field, and a first OCC indication field. Additionally, embodiments of this application may modify the MAC subheader of the MAC sub-PDU of successRAR in FIG4A to include one or more of the following indication fields: a second frequency domain indication field, a second time domain indication field, a length indication field, and a second OCC indication field.

[0213] It should be noted that the MAC subheaders involved in the embodiments of this application (e.g., the MAC subheader of the MAC sub-PDU used for backoff in Figure 4A; or the MAC subheader of the MAC sub-PDU used for rollback in Figure 4A; or the MAC subheader of any of the successRAR MAC sub-PDUs in Figure 4A) can be modified from the original header format by adding an indication field for applying the embodiments of this application; or, a new header can be defined, that is, including the indication field for applying the embodiments of this application; the embodiments of this application do not specifically limit this. Furthermore, there is no limitation on the order of the various fields and / or the number of bits occupied. The specific indication fields included in the MAC subheader can vary. The implementation methods of each MAC subheader will be described later in conjunction with different situations.

[0214] Of course, Figure 4A is only one possible message body structure, and the embodiments of this application are not limited to it. For ease of understanding, the embodiments of this application also provide the message body structure shown in Figure 4B. The difference between Figure 4B and Figure 4A is at least that: in Figure 4B, all sub-headers are uniformly set in a certain order in the MAC sub-header part, so that the UE can quickly decode the MAC sub-header and thus know whether the MAC PDU includes competition result information related to itself.

[0215] As shown in Figure 4B, this MAC PDU includes at least two parts: a MAC subheader and a MAC payload. The MAC subheader includes a BI subheader and a subheader corresponding to each response message. The MAC payload includes each response message. The order of the m subheaders in the MAC subheader can be consistent with the order of the m response messages in the MAC payload. For example, the m subheaders could be: subheader 1, subheader 2, subheader 3, ..., subheader m; correspondingly, the order of the m response messages in the MAC payload could be: response message 1, response message 2, response message 3, ..., response message m. The advantage of placing all the MAC subheaders corresponding to the response messages in the MAC subheader is that it facilitates faster decoding by the UE and helps improve decoding efficiency. Optionally, this MAC PDU may also include padding fields.

[0216] The response message in Figure 4B can be a response message indicating a rollback and / or a RAR / race resolution MAC CE indicating a successful race.

[0217] In some embodiments, the MAC payload portion in FIG4B may include some or all of the types of MAC sub-PDUs shown in FIG4A. A description of the MAC sub-PDUs can be found in FIG4A or the preceding description. For example, response message 1 in FIG4B is the MAC sub-PDU for rollback in FIG4A; response message 2 in FIG4B is the MAC sub-PDU for contention in FIG4A; response message 3 in FIG4B is the MAC sub-PDU for contention in FIG4A; ...; and so on. As another example, the BI sub-header in FIG4A may be located within the MAC sub-header in FIG4B.

[0218] It should be understood that the sorting relationship between the m subheadings and the m response messages shown in Figure 4B can also be sorted or corresponded according to other rules, and this is not limited.

[0219] It should be noted that Figure 4A or Figure 4B are merely possible message body structures shown and are only exemplary descriptions. The inclusion of Figure 4A or Figure 4B is for ease of understanding only and is not intended to limit the message body structure of the second message to the examples shown. Those skilled in the art can make flexible equivalent transformations or adjustments based on the message body structures shown in Figure 4A or Figure 4B, and the message body structures obtained from these equivalent transformations or adjustments all fall within the protection scope of the embodiments of this application.

[0220] In this embodiment, after receiving multiple first messages sent by multiple UEs in the same time domain and / or the same frequency domain, the network device responds to the first messages from the multiple UEs with a single second message. Compared to sending a response for each first message, multiplexing the responses to multiple first messages into a single message (such as the second message) significantly improves transmission efficiency. Furthermore, in this embodiment, by carrying a frequency domain indicator field and / or a time domain indicator field in the message body header, the UE can quickly determine whether a certain piece of information included in the second message is information about the outcome of a competition against itself, thereby improving decoding efficiency.

[0221] Since there are three scenarios for sending the first message at the same time domain location and / or the same frequency domain location, there are corresponding implementation methods for multiplexing the second message in each scenario. These will be described separately below.

[0222] Scenario 1: Multiple UEs send their own first messages at different frequency domain locations within the same time domain. Correspondingly, the network device receives these multiple first messages. That is, each UE has its own corresponding first message. When multiple UEs send their respective first messages, they may be sending them at different frequency domain locations within the same time domain. Accordingly, from the network device's perspective, the network device receives multiple first messages sent by multiple UEs at different frequency domain locations within the same time domain; in short, each of the multiple first messages received by the network device corresponds to one UE.

[0223] In some embodiments, for case 1, the second message includes at least a first MAC sub-PDU, the MAC sub-header of the first MAC sub-PDU including a second frequency domain indication field and / or a length indication field; the second frequency domain indication field is used to indicate the first frequency domain information.

[0224] For clarity, this application does not specifically limit the representation or granularity of the frequency domain location information indicated by the frequency domain indication field (e.g., the second frequency domain indication field or the first frequency domain indication field). The frequency domain location information indicated by the frequency domain indication field can be at the frequency point (e.g., f0) granularity, or at the frequency domain identifier (e.g., F1_ID), or at the physical resource block index / identifier (PRB index / ID); or it can be at the carrier granularity, for example, the first frequency domain information is the carrier identifier (carrier_ID).

[0225] For example, when multiple first messages are sent at different frequency domain locations at the same time domain location, the network device introduces a second frequency domain indication field into the MAC subheader of the first MAC sub-PDU, so that after decoding the MAC subheader, the UE can determine whether it has successfully competed, or whether the first MAC sub-PDU is related to itself, or whether to further decode the first MAC sub-PDU, based on the frequency domain information indicated by the second frequency domain indication field in the MAC subheader.

[0226] Taking the example of multiple UEs (including the first UE) sending a first message at a first frequency domain location, all multiple UEs can receive the second message sent by the network device. Taking the first UE as an example, the judgment process is described as follows: After receiving the second message, the first UE obtains the second frequency domain indication field by decoding the MAC sub-header of the first MAC sub-PDU in the second message. The second frequency domain indication field is used to indicate the first frequency domain information. The first UE determines whether the frequency domain location corresponding to the first frequency domain information is the same as the first frequency domain location used by itself to send the first message. Based on the judgment result, it determines whether the first MAC sub-PDU is related to itself, or whether the contention was successful, or whether to further decode the first MAC sub-PDU.

[0227] If it is determined that the frequency domain position corresponding to the first frequency domain information is the same as the first frequency domain position, then it is determined that the first MAC sub-PDU is related to itself, or the contention is successful, or the first MAC sub-PDU is further decoded.

[0228] If it is determined that the frequency domain position corresponding to the first frequency domain information is different from the first frequency domain position, the decoding of the first MAC sub-PDU is skipped; or, the decoding of data of the first length is skipped, the first length is determined based on the length indication field, and the next MAC sub-PDU or the next response information is decoded.

[0229] It should be noted that if the MAC header of the first MAC sub-PDU does not include a length indication field, the first UE may skip decoding of the first MAC sub-PDU or skip decoding of the default length. The default length may be the length of the first MAC sub-PDU, or the length of the first MAC sub-PDU and its associated MAC SDU and / or MAC CE. If the MAC header of the first MAC sub-PDU does not include a length indication field, the first UE determines the data decoding length to be skipped (e.g., a first length) based on the length indicated by the length indication field and skips the data decoding of the first length.

[0230] To clarify, if the frequency domain indication information (such as the first frequency domain information mentioned above) included in the MAC subheader of the first MAC subPDU sent by the network device determines that the first MAC subPDU is related to itself, then the meaning of "related" can be understood as: the frequency domain resources used by the first UE to send the first message are consistent with the frequency domain information indicated by the network device.

[0231] The aforementioned length indication field is used to indicate the length (or number of bits) of the skipped data decoding process. The purpose of introducing the length indication field is that, based on the judgment result of the aforementioned judgment process (i.e., the UE judges whether the frequency domain position corresponding to the first frequency domain information is the same as the first frequency domain position), if the UE determines that the first MAC sub-PDU is not related to itself, the length indication field can be used to determine the decoding length that needs to be skipped, thereby reducing unnecessary decoding processes, reducing the amount of decoding, and improving decoding efficiency.

[0232] It should be noted that the length indication field can directly or indirectly indicate the length of the skipped data decoding process. If the length indication field uses a direct indication method, the UE can directly skip the length indicated by the length indication field. If the length indication field uses an indirect indication method, the UE can further determine or calculate the length of the skipped data decoding based on the length indicated by the length indication field.

[0233] The length of data decoding skipped by the UE refers to the length of the entity of the first MAC sub-PDU; or, the sum of the length of the entity of the first MAC sub-PDU and the length of the MAC SDU and / or MAC CE associated with the first MAC sub-PDU. Optionally, the length indication field can indicate the length of the entity of the first MAC sub-PDU, and the sum of the lengths of the MAC SDU and / or MAC CE associated with the first MAC sub-PDU. It can indicate the length of the entity of the first MAC sub-PDU, or the length of the MAC subheader (e.g., the length occupied by the MAC subheader is represented as Subheader) and the entity of the MAC sub-PDU included in the first MAC sub-PDU, or the length of the MAC SDU and / or MAC CE associated with the first MAC sub-PDU. A MAC sub-PDU includes a MAC subheader; or, it includes a MAC subheader and the entity of the MAC sub-PDU.

[0234] The first MAC sub-PDU is introduced here for ease of description only and does not constitute a limitation on the embodiments of this application. Optionally, the first MAC sub-PDU includes a MAC sub-header and a contention success RAR (denoted as Success RAR); or, the first MAC sub-PDU is a contention resolution MAC CE (denoted as Contention Resolution MAC CE).

[0235] For example, assume the length indication field is represented as the L field; the first MAC sub-PDU includes a MAC subheader (represented as Subheader) and a Success RAR / contention resolution MAC CE. If the length L indicated by the L field is the data length of Success RAR / contention resolution MAC CE + subPDU + Subheader, then the data decoding length skipped by the UE is L. Here, Success RAR / contention resolution MAC CE is the length (or number of bits) occupied by this Success RAR / contention resolution MAC CE; subPDU is the length occupied by the MAC SDU or padding field following Success RAR / contention resolution MAC CE; and Subheader is the length (number of bits) occupied by the MAC subheader corresponding to the first MAC sub-PDU.

[0236] For example, if the length L indicated by the L field refers to the data length of the Success RAR / contention resolution MAC CE+subPDU, then the UE calculates the value of L+Subheader and skips the data decoding process of the corresponding length based on the calculation result.

[0237] For example, if the length L indicated by the L field refers to the length of the subPDU, then the UE calculates the value of L+Success RAR / contention resolution MAC CE+Subheader data length and skips the data decoding process of the corresponding length based on the calculation result.

[0238] For example, if the length L indicated by the L field refers to the length of the subPDU + Subheader, then the UE calculates the value of the data length of L + Success RAR / contention resolution MAC CE and skips the data decoding process of the corresponding length based on the calculation result.

[0239] The following describes an example format of the MAC header structure of the first MAC sub-PDU in Case 1, with reference to Figures 5A and 5B. Taking the first MAC sub-PDU as an example that it is a MAC sub-PDU used for successRAR, Figures 5A and 5B respectively show example formats of the MAC header of the first MAC sub-PDU without OCC application.

[0240] It should be understood that this description uses successRAR as an example only, and the embodiments of this application are not limited thereto. For example, the first MAC sub-PDU can also be a contention resolution MAC CE.

[0241] Figure 5A illustrates an example structure of the MAC sub-header newly introduced in this embodiment. As shown in Figure 5A, the MAC sub-header of the MAC sub-PDU for successRAR includes an Ff field (corresponding to the second frequency domain indication field mentioned above) and an L field (corresponding to the length indication field mentioned above). Optionally, the MAC sub-header also includes a reserved field (R field).

[0242] Figure 5B illustrates an example structure of this application embodiment with an added indicator field in the original MAC subheader. As shown in Figure 5B, the MAC subheader of the MAC sub-PDU for successRAR includes the E field, T1 field, T2 field, Ff field (corresponding to the second frequency domain indicator field mentioned above), and L field (corresponding to the length indicator field). Optionally, the MAC subheader also includes a reserved field (R field). The functions of the E field, T1 field, and T2 field can be found in the descriptions in related technologies, and will not be repeated here.

[0243] For clarity, this application does not specify the number of bits occupied by newly added indicator fields (including but not limited to one or more of the following: frequency domain indicator field, time domain indicator field, length indicator field, OCC indicator field, reserved field, etc.), the specific location of the newly added indicator fields in the MAC sub-header, or the order of the indicator fields. That is, the number of bits occupied by each indicator field or the order of the fields, and the location of the indicator fields in the message body structure (or sub-headers included in the message body) shown in the accompanying drawings (e.g., Figures 4A to 10D) are all exemplary descriptions.

[0244] As mentioned earlier, for multiple UEs sending the first message at different frequency domain locations within the same time domain, the network device can determine or indicate the UE sending the first message at the corresponding frequency domain location using the indicated frequency domain location information. However, further, if multiple UEs are sending the first message at the same frequency domain location, then for a UE receiving the second message, the network device can uniquely identify the UE using the OCC sequence indicated by the OOC indication field in the second message, or determine whether the MAC sub-PDU (such as the first MAC sub-PDU; or the response information used to carry the contention result) in the second message is related to itself, or determine whether to decode the first MAC sub-PDU (or the response information).

[0245] Similarly, for a unified explanation here, if the frequency domain indication information (such as the aforementioned first frequency domain information) and OCC indication field included in the MAC subheader of the first MAC subPDU sent by the first UE through the network device determine that the first MAC subPDU is related to itself, then the meaning of "related" can be understood as follows: the frequency domain resources used by the first UE to send the first message are consistent with the frequency domain information indicated by the network device; and the OCC sequence used by the first UE to send the first message is consistent with the OCC sequence indicated by the network device.

[0246] Taking the first MAC sub-PDU as an example, in some application scenarios, the UE cannot determine whether it has successfully competed for the MAC sub-PDU using the OCC sequence and frequency domain information indicated in the MAC sub-header. It can only determine whether the first MAC sub-PDU is related to itself, or whether to continue decoding the first MAC sub-PDU. This is because, taking two UEs as an example, if both UEs use the same OCC sequence and the network device only receives the first message from one of the UEs, then based on that OCC sequence, it cannot determine whether the competition was successful; it can only determine whether the first MAC sub-PDU is related to itself. When multiple UEs send the first message at the same frequency domain location within the same time domain, the UE can jointly determine whether the MAC sub-PDU (or response information) used to carry the competition result is related to itself, or whether to decode, through the frequency domain indication field and the OCC indication field. For example, if it is determined that the MAC sub-PDU used to carry the competition result is related to itself, the UE can decode it.

[0247] In some embodiments, when multiple UEs send a first message using an OCC sequence, the MAC sub-header (or response information) of the first MAC sub-PDU further includes a second OCC indication field. This second OCC indication field indicates the first OCC sequence, such as an OCC sequence index. The first OCC sequence represents the OCC sequence corresponding to the UE that successfully competed among the multiple UEs, or it represents the OCC sequence corresponding to the UE associated with the first MAC sub-PDU among the multiple UEs. Accordingly, based on the first OCC sequence and the frequency domain position corresponding to the first frequency domain information, the multiple UEs can jointly determine their own competition result information, or determine whether the first MAC sub-PDU is related to them, or determine whether to decode the first MAC sub-PDU (or response information).

[0248] For clarity, this application does not specifically limit the way the OCC indicator field indicates a certain OCC sequence. Optionally, the OCC indicator field can directly indicate the content of the OCC sequence, or it can indirectly indicate the OCC sequence, such as indicating the OCC sequence index. Based on the content indicated by the OCC indicator field, the UE can determine whether the indicated OCC sequence is the same as the OCC sequence it is using.

[0249] Taking the first UE as an example, the first UE determines whether the first frequency domain information indicated by the second frequency domain indication field is the same as the first frequency domain position, and determines whether the OCC sequence used by the first UE to send the first message is the same as the first OCC sequence. If the frequency domain position corresponding to the first frequency domain information is the same as the first frequency domain position, and the OCC sequence used by the first UE to send the first message is the same as the first OCC sequence, the first MAC sub-PDU is determined to be related to the first UE, or the first UE is determined to decode the first MAC sub-PDU. If the frequency domain position corresponding to the first frequency domain information is different from the first frequency domain position, and / or the OCC sequence used by the first UE to send the first message is different from the first OCC sequence, the first UE is determined to be unrelated to itself, or the first UE is determined not to decode the first MAC sub-PDU, or the first UE is determined to skip decoding the first MAC sub-PDU, or the first length of data decoding is determined based on the length indication field. The first length is determined based on the length indication field.

[0250] This section describes how a UE determines whether an OCC sequence is the same as the OCC sequence it is using, based on the OCC indicator field (which can be represented as the C field, and the C field can indicate the index of various OCC sequences through different bit values).

[0251] For example, if two OCC sequences are used, the C field occupies 1 bit and can be set to 0 or 1 to indicate OCC sequence index 0 and OCC sequence index 1, respectively. If the OCC sequence used by the UE to send CB-MSG3 is OCC sequence 1 and the C field indicates 1, then the OCC sequence indicated by the C field is the same as the OCC sequence used by the UE to send CB-MSG3, and vice versa.

[0252] It should be understood that the aforementioned correspondence between the value of 1 bit and the OCC sequence index value is merely an exemplary description, and the embodiments of this application are not limited thereto. For example, the values ​​0 and 1 can be used to indicate OCC sequence index 1 and OCC sequence index 0, respectively.

[0253] For example, if four OCC sequences are used, the C field occupies two bits, and the values ​​00, 01, 10, and 11 can be used to indicate the corresponding OCC sequence index 00, OCC sequence index 01, OCC sequence index 10, and OCC sequence index 11, respectively. If the OCC sequence used by the UE to send CB-MSG3 is OCC sequence 1, and the C field indicates 01, then it means that the OCC sequence indicated by the C field is the same as the OCC sequence used by the UE to send CB-MSG3. If the C field indicates other values, it means that they are different.

[0254] It should be understood that the above correspondence between the 2-bit values ​​and the OCC sequence index values ​​is merely an exemplary description, and the embodiments of this application are not limited thereto. For example, the values ​​00, 01, 10, and 11 can be used to indicate the corresponding OCC sequence index 11, OCC sequence index 10, OCC sequence index 01, and OCC sequence index 00, respectively; they will not be listed here one by one.

[0255] It should also be understood that the OCC sequence and the number of bits occupied by the C field described herein are merely illustrative examples, and the embodiments of this application are not limited thereto.

[0256] The implementation of the length indicator field can be found in the previous description; for the sake of brevity, it will not be repeated here.

[0257] Taking the example that the first MAC sub-PDU is a MAC sub-PDU used for SuccessRAR, Figures 5C and 5D show example formats of the MAC sub-header of the first MAC sub-PDU, respectively. Compared to Figures 5A and 5B, the formats in Figures 5C and 5D add a C field (used to indicate the OCC sequence) to suit OCC scenarios. The C field is an example of a second OCC indicator field.

[0258] Figure 5C illustrates an example structure of the MAC sub-header newly introduced in this application embodiment. As shown in Figure 5C, the MAC sub-header for the MAC sub-PDU used for successRAR includes the Ff field, C field, and L field. Optionally, the MAC sub-header also includes a reserved field (R field).

[0259] Figure 5D illustrates an example structure of this application embodiment with an added indicator field in the original MAC subheader. As shown in Figure 5D, the MAC subheader of the MAC sub-PDU for successRAR includes the E field, T1 field, T2 field, Ff field, C field, and L field. Optionally, the MAC subheader also includes a reserved field (R field). The functions of the E field, T1 field, and T2 field can be found in the descriptions in related technologies, and will not be repeated here.

[0260] It is hereby stated that the embodiments of this application do not specifically limit the number of bits occupied by the newly added indicator field, the specific position of the newly added indicator field in the MAC subheader, or the order of the indicator fields.

[0261] As mentioned earlier, when the second message is sent as a MAC PDU message, the MAC PDU message may also include a MAC sub-PDU for rollback. The following describes the implementation of the MAC sub-PDU for rollback in Case 1.

[0262] Optionally, the MAC subheader of the MAC subPDU used for rollback includes a first frequency domain indication field, which indicates second frequency domain information.

[0263] Figures 6A and 6B respectively show example structural diagrams of the MAC sub-header of the MAC sub-PDU for fallback in Case 1. As shown in Figure 6A, the MAC sub-header of the MAC sub-PDU for fallback in this embodiment includes an Ff field (corresponding to the first frequency domain indication field mentioned above). Optionally, the MAC sub-header also includes a reserved field (R field).

[0264] Figure 6B illustrates an example structure of this application embodiment with an added indicator field in the original MAC subheader. As shown in Figure 6B, the MAC subheader of the MAC subPDU used for fallback includes an E field, a T1 field, and an Ff field (corresponding to the first frequency domain indicator field mentioned above). Optionally, the MAC subheader also includes a reserved field (R field). The functions of the E field and the T1 field can be found in the descriptions in related technologies, and will not be repeated here.

[0265] For example, when the first UE decodes the MAC sub-PDU used for fallback, it can determine whether the frequency domain position corresponding to the second frequency domain information indicated by the first frequency domain indicator field in the corresponding MAC sub-header is the same as the first frequency domain position used by itself to send the first message. If the frequency domain position corresponding to the second frequency domain information is the same as the first frequency domain position, the first UE performs a fallback operation, for example, fallback to the four-step random access procedure. For a detailed description of the four-step random access procedure, please refer to relevant technologies, which will not be elaborated here. If the frequency domain position corresponding to the second frequency domain information is different from the first frequency domain position, it is determined that it is unrelated to the MAC sub-PDU used for fallback; further, for example, the first UE can continue to decode the next MAC sub-PDU used for fallback.

[0266] In some embodiments, in scenarios where multiple UEs apply OCC sequences, the MAC subheader of the MAC subPDU used for fallback further includes a first OCC indication field; the first OCC indication field is used to indicate a second OCC sequence, which represents the OCC sequence used by the UE performing the fallback operation. Similarly, in cases where multiple UEs send the first message at the same frequency domain location, the UE can be identified through the OCC sequence.

[0267] For example, when the first UE reads the Ff field and C field of the MAC subheader of the MAC sub-PDU used for fallback, it can determine whether the MAC sub-PDU used for fallback is related to itself based on the reading results of the Ff field and C field.

[0268] The specific indication method of the OCC indicator field, such as the value of the bits occupied by the OCC indicator field and the correspondence between them and the OCC sequence index, is similar to the indication method mentioned above. For the sake of brevity, it will not be described in detail here.

[0269] In some embodiments, a rollback operation is performed when the frequency domain position corresponding to the second frequency domain information is the same as the first frequency domain position, and the OCC sequence used by the first UE to send the first message is the same as the second OCC sequence. For example, if the frequency domain position indicated by the Ff domain is the same as the frequency domain position used by the first UE, and the OCC sequence indicated by the C domain (the second OCC sequence) is the same as the OCC sequence used by the UE, then it is determined that the MAC sub-PDU used for rollback is related to the UE, and a rollback operation is performed.

[0270] In other embodiments, if the frequency domain position corresponding to the second frequency domain information is different from the first frequency domain position, and / or the OCC sequence used by the first UE to send the first message is different from the second OCC sequence, it is determined that the MAC sub-PDU used for rollback is irrelevant. For example, if the frequency domain position indicated by the Ff domain is different from the frequency domain position used by the first UE, and / or the OCC sequence indicated by the C domain (the second OCC sequence) is different from the OCC sequence used by the UE, then it is determined that the MAC sub-PDU used for rollback is irrelevant to the UE, and the rollback operation is not performed.

[0271] Figures 6C and 6D show example formats of the MAC subheader for the MAC sub-PDU used for rollback. Compared to Figures 6A and 6B, the formats in Figures 6C and 6D add a C field (for indicating the OCC sequence) to suit OCC scenarios. The C field is an example of the aforementioned first OCC indication field.

[0272] Figure 6C illustrates an example structure of the MAC sub-header newly introduced in this application embodiment for the MAC sub-PDU used for rollback. As shown in Figure 6C, the MAC sub-header of the MAC sub-PDU used for rollback includes an Ff field and a C field. Optionally, the MAC sub-header also includes a reserved field (R field).

[0273] Figure 6D illustrates an example structure of a MAC sub-PDU for rollback in this application, where an indicator field is added to the original MAC sub-header. As shown in Figure 6D, the MAC sub-header of the MAC sub-PDU for rollback includes the E field, T1 field, Ff field, and C field. Optionally, the MAC sub-header also includes a reserved field (R field). The functions of the E field and T1 field can be found in the descriptions in related technologies, and will not be repeated here.

[0274] As mentioned earlier, when the second message is sent as a MAC PDU message, the MAC PDU message may also include a MAC sub-PDU for backoff. The following describes the implementation of the MAC sub-PDU for backoff in Case 1.

[0275] Optionally, the MAC subheader of the MAC sub-PDU used for backoff includes a third frequency domain indicator field, which indicates third frequency domain information.

[0276] Figures 6E and 6F respectively show example structural diagrams of the MAC subheader for the MAC sub-PDU used for backoff in Case 1. As shown in Figure 6E, the MAC subheader of the MAC sub-PDU used for backoff in this embodiment includes an Ff field (corresponding to the third frequency domain indication field mentioned above). Optionally, the MAC subheader also includes a reserved field (R field).

[0277] Figure 6F illustrates an example structure of this application embodiment with a newly added indicator field in the original BI subheader. As shown in Figure 6F, the MAC subheader of the MAC subPDU used for backoff includes an E field, a T1 field, and an Ff field (corresponding to the third frequency domain indicator field mentioned above). Optionally, the MAC subheader also includes a reserved field (R field). The functions of the E field and the T1 field can be found in the description in related technologies, and will not be repeated here.

[0278] For example, when the first UE decodes a MAC sub-PDU used for backoff, it can determine whether the frequency domain position corresponding to the third frequency domain information indicated by the third frequency domain indicator field in the corresponding MAC sub-header is the same as the first frequency domain position used by itself to send the first message. If the frequency domain position corresponding to the third frequency domain information is the same as the first frequency domain position, the first UE performs a backoff operation, for example, waiting for a certain period of time before sending the first message. A detailed description of the backoff operation can be found in related technologies and will not be elaborated here. If the frequency domain position corresponding to the third frequency domain information is different from the first frequency domain position, it is determined that it is unrelated to the MAC sub-PDU used for backoff; further, for example, the first UE can decode the next MAC sub-PDU of the MAC sub-PDU used for backoff.

[0279] In some embodiments, in scenarios where multiple UEs apply OCC sequences, the MAC subheader of the MAC sub-PDU used for backoff further includes a third OCC indication field; the third OCC indication field is used to indicate a seventh OCC sequence, where the second OCC sequence represents the OCC sequence used by the UE performing the backoff operation. Similarly, in cases where multiple UEs transmit the first message at the same frequency domain location, the UE can be determined using the OCC sequence.

[0280] For example, when the first UE reads the Ff field and C field of the MAC subheader of the MAC sub-PDU used for backoff, it can determine whether the MAC sub-PDU used for backoff is related to itself based on the reading results of the Ff field and C field.

[0281] The specific indication method of the OCC indicator field, such as the value of the bits occupied by the OCC indicator field and the correspondence between them and the OCC sequence index, is similar to the indication method mentioned above. For the sake of brevity, it will not be described in detail here.

[0282] In some embodiments, a backoff operation is performed when the frequency domain position corresponding to the third frequency domain information is the same as the first frequency domain position, and the OCC sequence used by the first UE to send the first message is the same as the seventh OCC sequence. For example, if the frequency domain position indicated by the Ff domain is the same as the frequency domain position used by the first UE, and the OCC sequence indicated by the C domain (the second OCC sequence) is the same as the OCC sequence used by itself, then it is determined that the MAC sub-PDU used for backoff is related to itself, and a backoff operation is performed.

[0283] In other embodiments, if the frequency domain position corresponding to the third frequency domain information is different from the first frequency domain position, and / or the OCC sequence used by the first UE to send the first message is different from the seventh OCC sequence, it is determined that the MAC sub-PDU used for backoff is irrelevant. For example, if the frequency domain position indicated by the Ff domain is different from the frequency domain position used by the first UE, and / or the OCC sequence indicated by the C domain (the second OCC sequence) is different from the OCC sequence used by the UE, then it is determined that the MAC sub-PDU used for backoff is irrelevant to the UE, and the backoff operation is not performed.

[0284] Figures 6G and 6H show example formats of the MAC subheader for a MAC sub-PDU used for backoff. Compared to Figures 6E and 6F, the formats in Figures 6G and 6H add a C field (for indicating the OCC sequence) to suit OCC scenarios. The C field is an example of the aforementioned third OCC indication field.

[0285] Figure 6G illustrates an example structure of the MAC subheader newly introduced in this application embodiment for a MAC sub-PDU used for backoff. As shown in Figure 6G, the MAC subheader for a MAC sub-PDU used for backoff includes an Ff field and a C field. Optionally, the MAC subheader also includes a reserved field (R field).

[0286] Figure 6H illustrates an example structure of a MAC sub-PDU for backoff with an added indicator field in the original MAC sub-header, according to an embodiment of this application. As shown in Figure 6H, the MAC sub-header of the MAC sub-PDU for backoff includes the E field, T1 field, T2 subfield, Ff field, and C field. Optionally, the MAC sub-header also includes a reserved field (R field). The functions of the E field, T1 field, and T2 subfield can be found in the descriptions in related technologies, and will not be repeated here.

[0287] Scenario 2: Multiple UEs send multiple first messages at different time domain locations within the same frequency domain. Correspondingly, the network device receives these multiple first messages. That is, each UE has its own corresponding first message. When multiple UEs send their respective first messages, they may be sending them at different time domain locations within the same frequency domain. Accordingly, from the network device's perspective, the network device receives the first messages sent by multiple UEs at different time domain locations within the same frequency domain; in short, each of the multiple first messages received by the network device corresponds to one UE.

[0288] In some embodiments, for case 2, the second message includes a second MAC sub-PDU, the MAC sub-header of the second MAC sub-PDU including a second time domain indication field and / or a length indication field; the second time domain indication field is used to indicate the first time domain information.

[0289] For clarity, this application does not specifically limit the representation or granularity of the time-domain location information indicated by the time-domain indication field (such as the first or second time-domain indication field). The time-domain location information indicated by the time-domain indication field may include, but is not limited to, one or more of the following: system frame number (SFN), radio frame number, hyperframe number (H-SFN), subframe index, slot number or OFDM symbol, time-domain location number within a predefined period, resource number in a resource window used to send the first message or a copy of the first message, etc. For example, the predefined time-domain location number within a period represents the Nth time-domain resource within a time-domain resource period. Similarly, the resource number in a resource window used to send the first message or a copy of the first message represents the Nth resource or set of resources in the resource window used to send the first message or a copy of the first message.

[0290] For example, when multiple first messages are sent at different time domain locations in the same frequency domain, the network device introduces a second time domain indication field into the MAC subheader of the second MAC sub-PDU, so that the UE can determine whether it has successfully competed, or whether to decode the second MAC sub-PDU, or whether the second MAC sub-PDU is related to itself by decoding the time domain information indicated by the second time domain indication field in the MAC subheader.

[0291] Similarly, for a unified explanation here, if the time domain indication information (such as the first time domain information mentioned above) included in the MAC subheader of the second MAC subPDU sent by the network device determines that the second MAC subPDU is related to itself, then the meaning of "related" can be understood as: the time domain resources used by the first UE to send the first message are consistent with the time domain information indicated by the network device.

[0292] Taking the example of multiple UEs (including the first UE) sending a first message at a first time domain location, all multiple UEs can receive the second message sent by the network device. Taking the first UE as an example, the process of reading the MAC sub-header is described. After receiving the second message, the first UE obtains the second time domain indication field by decoding the MAC sub-header of the second MAC sub-PDU in the second message. The second time domain indication field is used to indicate the first time domain information. The first UE determines whether the time domain location corresponding to the first time domain information is the same as the first time domain location used to send the first message, so as to determine whether the second MAC sub-PDU is related to itself, or whether to skip the decoding of the second MAC sub-PDU, or whether to skip the decoding of data of the second length (the second length is determined based on the length indication field, including the length indication field).

[0293] If it is determined that the time domain position corresponding to the first time domain information is the same as the first time domain position, then the second MAC sub-PDU is determined to be related to itself, or the second MAC sub-PDU is determined to be decoded.

[0294] If it is determined that the time domain position corresponding to the first time domain information is different from the first time domain position, the decoding of the second MAC sub-PDU is skipped, or the data decoding of the second length is skipped, the second length is determined based on the length indication field, and the next MAC sub-PDU is decoded.

[0295] Regarding whether the length for skipping data decoding is the default length or the second length, please refer to the relevant description in Case 1, which will not be elaborated here.

[0296] For a description of the length indication field and its implementation, please refer to the previous text. Similarly, if the UE determines that the second MAC sub-PDU is unrelated to itself, it can determine the decoding length to be skipped based on the length indication field, thereby reducing unnecessary decoding processes, reducing the amount of decoding, and improving decoding efficiency.

[0297] The following describes an example of the MAC header structure of the second MAC sub-PDU with reference to Figures 7A and 7B. Taking the second MAC sub-PDU as an example that is a MAC sub-PDU used for successRAR, Figures 7A and 7B respectively show example formats of the MAC header of the second MAC sub-PDU without OCC application.

[0298] Figure 7A illustrates an example structure of the MAC sub-header newly introduced in this application embodiment. As shown in Figure 7A, the MAC sub-header of the MAC sub-PDU for successRAR includes a T field (corresponding to the second time domain indication field mentioned above) and an L field (corresponding to the length indication field mentioned above). Optionally, the MAC sub-header also includes a reserved field (R field).

[0299] Figure 7B illustrates an example structure of this application embodiment with an added indicator field in the original MAC subheader. As shown in Figure 7B, the MAC subheader of the MAC sub-PDU for successRAR includes the E field, T1 field, T2 field, T field (corresponding to the second time domain indicator field mentioned above), and L field (corresponding to the length indicator field mentioned above). Optionally, the MAC subheader also includes a reserved field (R field). The functions of the E field, T1 field, and T2 field can be found in the descriptions in related technologies, and will not be repeated here.

[0300] For multiple UEs sending the first message at different time-domain locations within the same frequency domain, the network device can determine the UE sending the first message at the corresponding time-domain location using the indicated time-domain location information. Furthermore, if multiple UEs send the first message at the same time-domain location, the UE receiving the second message can be uniquely identified by the OCC sequence indicated by the OOC indication field in the second message, or by determining whether the MAC sub-PDU (e.g., the second MAC sub-PDU; or the response information carrying the contention result) in the second message is relevant to itself, or by determining whether to decode the second MAC sub-PDU (or the response information).

[0301] Similarly, for a unified explanation here, if the time domain indication information (such as the first time domain information mentioned above) and OCC indication field included in the MAC subheader of the second MAC subPDU sent by the network device determine that the second MAC subPDU is related to itself, then the meaning of "related" can be understood as follows: the time domain resources used by the first UE to send the first message are consistent with the time domain information indicated by the network device; and the OCC sequence used by the first UE to send the first message is consistent with the OCC sequence indicated by the network device.

[0302] Taking the second MAC sub-PDU as an example, in some application scenarios, the UE cannot determine whether it has successfully completed the contention based solely on the OCC sequence and time-frequency information indicated in the MAC sub-header. It can only determine whether the second MAC sub-PDU is related to itself, or whether to continue decoding the second MAC sub-PDU. This is because, taking two UEs as an example, if both UEs use the same OCC sequence and the network device only receives the first message from one of the UEs, then based on that OCC sequence, it cannot determine whether the contention was successful; it can only determine whether the first MAC sub-PDU is related to itself.

[0303] When multiple UEs send the first message at the same time domain location within the same frequency domain, the UE can jointly determine, through the time domain indication field and the OCC indication field, whether the MAC sub-PDU (or response information) used to carry the contention result is related to itself, or whether to continue decoding. For example, if it is determined that the MAC sub-PDU used to carry the contention result is related to itself, the UE can continue decoding.

[0304] In some embodiments, when multiple UEs send a first message using an OCC sequence, the MAC subheader of the second MAC subPDU further includes a second OCC indication field; the second OCC indication field is used to indicate a third OCC sequence; the third OCC sequence represents the OCC sequence corresponding to the UE associated with the second MAC subPDU among the multiple UEs, or the OCC sequence corresponding to the UE that successfully competes for the second MAC subPDU among the multiple UEs. Accordingly, based on the third OCC sequence and the time domain position corresponding to the first time domain information, the multiple UEs can determine whether the second MAC subPDU is associated with them, or whether to decode the second MAC subPDU (or response information), or whether to skip decoding the second MAC subPDU.

[0305] Taking the first UE as an example, the first UE determines whether the time domain position corresponding to the first time domain information indicated by the second time domain indication field is the same as the first time domain position, and determines whether the OCC sequence used by the first UE to send the first message is the same as the third OCC sequence. If the time domain position corresponding to the first time domain information is the same as the first time domain position, and the OCC sequence used by the first UE to send the first message is the same as the third OCC sequence, the first UE determines that the second MAC sub-PDU is related to the first UE, or determines to decode the second MAC sub-PDU. If the time domain position corresponding to the first time domain information is different from the first time domain position, and / or the OCC sequence used by the first UE to send the first message is different from the third OCC sequence, the first UE determines that the second MAC sub-PDU is not related to itself, or determines not to decode the second MAC sub-PDU, or skips the decoding of the second MAC sub-PDU, or skips the decoding of data of the second length, which is determined based on the length indication field.

[0306] The implementation of the length indicator field can be found in the previous description; for the sake of brevity, it will not be repeated here.

[0307] Taking the example that the second MAC sub-PDU is a MAC sub-PDU used for successRAR, Figures 7C and 7D show example formats of the MAC sub-header of the second MAC sub-PDU, respectively. Compared to Figures 7A and 7B, the formats in Figures 7C and 7D add a C field (used to indicate the OCC sequence) to suit OCC scenarios. The C field is an example of the aforementioned second OCC indication field.

[0308] Figure 7C illustrates an example structure of the MAC sub-header newly introduced in this application embodiment. As shown in Figure 7C, the MAC sub-header for the MAC sub-PDU used for successRAR includes a T field, a C field, and an L field. Optionally, the MAC sub-header also includes a reserved field (R field).

[0309] Figure 7D illustrates an example structure of this application embodiment with a newly added indicator field in the original MAC subheader. As shown in Figure 7D, the MAC subheader of the MAC sub-PDU for successRAR includes the E field, T1 field, T2 field, T field, C field, and L field. Optionally, the MAC subheader also includes a reserved field (R field). The functions of the E field, T1 field, and T2 field can be found in the descriptions in related technologies, and will not be repeated here.

[0310] As mentioned earlier, when the second message is sent as a MAC PDU message, the MAC PDU message may also include a MAC sub-PDU for rollback. The following describes the implementation of the MAC sub-PDU for rollback in scenario 2.

[0311] Optionally, the MAC subheader of the MAC subPDU used for rollback includes a first time domain indicator field; the first time domain indicator field is used to indicate second time domain information.

[0312] Figures 8A and 8B respectively show example structural diagrams of the MAC sub-header of the MAC sub-PDU for rollback in case 2. As shown in Figure 8A, the MAC sub-header of the MAC sub-PDU for rollback in this embodiment includes a T field (corresponding to the first time domain indication field mentioned above). Optionally, the MAC sub-header also includes a reserved field (R field).

[0313] Figure 8B illustrates an example structure of this application embodiment with a newly added indicator field in the original MAC subheader. As shown in Figure 8B, the MAC subheader of the MAC subPDU used for rollback includes an E field, a T1 field, and a T field (corresponding to the first time domain indicator field mentioned above). Optionally, the MAC subheader also includes a reserved field (R field). The functions of the E field and the T1 field can be found in the description in related technologies, and will not be repeated here.

[0314] For example, when the first UE decodes the MAC sub-PDU used for fallback, it can determine whether the time domain position corresponding to the second time domain information indicated by the first time domain indicator field in the corresponding MAC sub-header is the same as the first time domain position used by itself when sending the first message. If the time domain position corresponding to the second time domain information is the same as the first time domain position, a fallback operation is performed, for example, fallback to the four-step random access procedure. If the time domain position corresponding to the second time domain information is different from the first time domain position, it is determined that it is unrelated to the MAC sub-PDU used for fallback.

[0315] In some embodiments, in scenarios where multiple UEs apply OCC sequences, the MAC subheader of the MAC subPDU used for fallback further includes a first OCC indication field; the first OCC indication field is used to indicate a fourth OCC sequence, which represents the OCC sequence used by the UE performing the fallback operation among multiple UEs that send the first message at different time domain locations. Similarly, in cases where multiple UEs send the first message at the same time domain location, the UE can be determined using the OCC sequence.

[0316] For example, when the first UE reads the T field and C field of the MAC subheader of the MAC sub-PDU used for rollback, it can determine whether the MAC sub-PDU used for rollback is related to itself based on the reading results of the T field and C field.

[0317] In some embodiments, a rollback operation is performed when the time domain location corresponding to the second time domain information is the same as the first time domain location, and the OCC sequence used by the first UE to send the first message is the same as the fourth OCC sequence. For example, if the time domain location indicated by the T domain is the same as the time domain location used by the first UE, and the OCC sequence indicated by the C domain (the fourth OCC sequence) is the same as the OCC sequence used by the UE, then it is determined that the MAC sub-PDU used for rollback is related to the UE, and a rollback operation is performed.

[0318] In other embodiments, if the time domain position corresponding to the second time domain information is different from the first time domain position, and / or the OCC sequence used by the first UE to send the first message is different from the fourth OCC sequence, it is determined that the MAC sub-PDU used for fallback is irrelevant. For example, if the time domain position indicated by the T domain is different from the time domain position used by the first UE, and / or the OCC sequence indicated by the C domain (the fourth OCC sequence) is different from the OCC sequence used by itself, then it is determined that the MAC sub-PDU used for fallback is irrelevant to itself.

[0319] Figures 8C and 8D show example formats of the MAC subheader for the MAC sub-PDU used for rollback. Compared to Figures 8A and 8B, the formats in Figures 8C and 8D add a C field (for indicating the OCC sequence) to suit OCC scenarios. The C field is an example of the aforementioned first OCC indication field.

[0320] Figure 8C illustrates an example structure of the MAC sub-header newly introduced in this application embodiment for a MAC sub-PDU used for rollback. As shown in Figure 8C, the MAC sub-header for the MAC sub-PDU used for rollback includes a T field and a C field. Optionally, the MAC sub-header also includes a reserved field (R field).

[0321] Figure 8D illustrates an example structure of a MAC sub-PDU for rollback in this application, where an indicator field is added to the original MAC sub-header. As shown in Figure 8D, the MAC sub-header of the MAC sub-PDU for rollback includes the E field, T1 field, T field, and C field. Optionally, the MAC sub-header also includes a reserved field (R field). The functions of the E field and T1 field can be found in the descriptions in related technologies, and will not be repeated here.

[0322] As mentioned earlier, when the second message is sent as a MAC PDU message, the MAC PDU message may also include a MAC sub-PDU for backoff. The following describes the implementation of the MAC sub-PDU for backoff in scenario 2.

[0323] Optionally, the MAC subheader of the MAC subPDU used for backoff includes a third time domain indicator field; the third time domain indicator field is used to indicate third time domain information.

[0324] Figures 8E and 8F respectively show example structural diagrams of the MAC subheader for the MAC sub-PDU used for backoff in Case 2. As shown in Figure 8E, the MAC subheader of the MAC sub-PDU used for backoff in this embodiment includes a T field (corresponding to the third time domain indication field mentioned above). Optionally, the MAC subheader also includes a reserved field (R field).

[0325] Figure 8F illustrates an example structure of this application embodiment with an added indicator field in the original MAC subheader. As shown in Figure 8F, the MAC subheader of the MAC subPDU used for backoff includes an E field, a T1 field, and a T field (corresponding to the third time domain indicator field mentioned above). Optionally, the MAC subheader also includes a reserved field (R field). The functions of the E field and the T1 field can be found in the description in related technologies, and will not be repeated here.

[0326] For example, when the first UE decodes the MAC sub-PDU used for backoff, it can determine whether the time domain position corresponding to the third time domain information indicated by the third time domain indication field in the corresponding MAC sub-header is the same as the first time domain position used by itself to send the first message. If the time domain position corresponding to the third time domain information is the same as the first time domain position, a backoff operation is performed, for example, waiting for a certain period of time before sending the first message. If the time domain position corresponding to the third time domain information is different from the first time domain position, it is determined that it is unrelated to the MAC sub-PDU used for backoff.

[0327] In some embodiments, in scenarios where multiple UEs apply OCC sequences, the MAC subheader of the MAC subPDU used for backoff further includes a third OCC indication field; the third OCC indication field is used to indicate an eighth OCC sequence, which represents the OCC sequence used by the UE performing the backoff operation among multiple UEs that send the first message at different time domain locations. Similarly, in cases where multiple UEs send the first message at the same time domain location, the UE can be determined by the OCC sequence.

[0328] For example, when the first UE reads the T field and C field of the MAC subheader of the MAC sub-PDU used for backoff, it can determine whether the MAC sub-PDU used for backoff is related to itself based on the reading results of the T field and C field.

[0329] In some embodiments, a backoff operation is performed when the time domain location corresponding to the third time domain information is the same as the first time domain location, and the OCC sequence used by the first UE to send the first message is the same as the eighth OCC sequence. For example, if the time domain location indicated by the T domain is the same as the time domain location used by the first UE, and the OCC sequence indicated by the C domain (the eighth OCC sequence) is the same as the OCC sequence used by the UE, then it is determined that the MAC sub-PDU used for backoff is related to the UE, and a backoff operation is performed.

[0330] In other embodiments, if the time domain position corresponding to the third time domain information is different from the first time domain position, and / or the OCC sequence used by the first UE to send the first message is different from the eighth OCC sequence, it is determined that the MAC sub-PDU used for backoff is irrelevant. For example, if the time domain position indicated by the T domain is different from the time domain position used by the first UE, and / or the OCC sequence indicated by the C domain (eighth OCC sequence) is different from the OCC sequence used by itself, then it is determined that the MAC sub-PDU used for backoff is irrelevant to itself.

[0331] Figures 8G and 8H show example formats of the MAC subheader for a MAC sub-PDU used for backoff. Compared to Figures 8E and 8F, the formats in Figures 8G and 8H add a C field (for indicating the OCC sequence) to suit OCC scenarios. The C field is an example of the aforementioned third OCC indication field.

[0332] Figure 8G illustrates an example structure of the MAC sub-header newly introduced in this application embodiment for a MAC sub-PDU used for backoff. As shown in Figure 8G, the MAC sub-header for a MAC sub-PDU used for backoff includes a T field and a C field. Optionally, the MAC sub-header also includes a reserved field (R field).

[0333] Figure 8H illustrates an example structure of a MAC sub-PDU for backoff with an added indicator field in the original MAC sub-header, according to an embodiment of this application. As shown in Figure 8H, the MAC sub-header of the MAC sub-PDU for backoff includes the E field, T1 field, T2 field, T field, and C field. Optionally, the MAC sub-header also includes a reserved field (R field). The functions of the E field, T1 field, and T2 field can be found in the descriptions in related technologies, and will not be repeated here.

[0334] In summary, cases 1 and 2 above either include a frequency domain indicator field (or further include an OCC indicator field) or a time domain indicator field (or further include an OCC indicator field). In one possible implementation, the implementations of the frequency domain indicator field and the time domain indicator field can also be combined. Optionally, as a possible implementation, the subheader of the second message may also include both a frequency domain indicator field and a time domain indicator field.

[0335] Scenario 3: Multiple UEs send multiple first messages at the same frequency and time domain locations. Correspondingly, the network device receives these multiple first messages. That is, each UE has its own corresponding first message. When multiple UEs send their respective first messages, they may be sending them at the same time and frequency domain locations. Accordingly, from the network device's perspective, the network device will receive multiple first messages sent by multiple UEs at the same time and frequency domain locations; in short, each of the multiple first messages received by the network device corresponds to one UE.

[0336] In some embodiments, for case 3, the second message includes a third MAC sub-PDU, the MAC sub-header of which includes a second OCC indication field and / or a length indication field; the second OCC indication field is used to indicate a fifth OCC sequence, which represents the OCC sequence corresponding to the UE associated with the fifth MAC sub-PDU among multiple UEs that send the first message at the same frequency domain location and the same time domain location, or the OCC sequence corresponding to the UE that successfully competes for the message.

[0337] Similarly, for a unified explanation here, if the first UE determines that the third MAC sub-PDU is related to itself by including the MAC sub-header and the OCC indication field in the third MAC sub-PDU sent by the network device, then the meaning of "related" can be understood as: the OCC sequence used by the first UE to send the first message is consistent with the OCC sequence indicated by the network device.

[0338] For example, when multiple first messages are sent at the same time-frequency domain location, the network device introduces a second OCC indication field in the MAC subheader of the third MAC sub-PDU.

[0339] Taking the example of multiple UEs (including the first UE) sending a first message at a first time-frequency domain location, all multiple UEs can receive the second message sent by the network device. Taking the first UE as an example, the process of reading the MAC sub-header is described. After receiving the second message, the first UE obtains the second OCC indication field by decoding the MAC sub-header of the third MAC sub-PDU in the second message. The second OCC indication field is used to indicate the fifth OCC sequence. The first UE determines whether the fifth OCC sequence is the same as the OCC sequence it used to send the first message; based on the determination result, it decides whether to determine whether it is related to the third MAC sub-PDU; or, whether to decode the third MAC sub-PDU; or, whether to skip decoding the third MAC sub-PDU.

[0340] If it is determined that the OCC sequence used by the first UE to send the first message is the same as the fifth OCC sequence, it is determined that it is related to the third MAC sub-PDU, or it is determined that the third MAC sub-PDU is further decoded, or it is determined that the contention is successful.

[0341] If it is determined that the OCC sequence used by the first UE to send the first message is different from the fifth OCC sequence, it is determined that it is unrelated to the third MAC sub-PDU, or the decoding of the third MAC sub-PDU is skipped, or the data decoding of the third length is skipped, the third length being determined based on the length indication field.

[0342] For a description of the length indication field and its implementation, please refer to the preceding text. Similarly, if the UE determines that the third MAC sub-PDU is unrelated to itself, it can determine the decoding length to be skipped based on the length indication field, or skip the decoding of the MAC sub-PDU, thereby reducing unnecessary decoding processes, reducing the amount of decoding, and improving decoding efficiency.

[0343] The following describes an example of the MAC header structure of the third MAC sub-PDU with reference to Figures 9A and 9B. Taking the third MAC sub-PDU as an example that it is a MAC sub-PDU used for successRAR, Figures 9A and 9B show example formats of the MAC header of the third MAC sub-PDU when OCC is applied.

[0344] Figure 9A illustrates an example structure of the MAC sub-header newly introduced in this embodiment. As shown in Figure 9A, the MAC sub-header of the MAC sub-PDU for successRAR includes a C field (corresponding to the second OCC indicator field mentioned above) and an L field (corresponding to the length indicator field mentioned above). Optionally, the MAC sub-header also includes a reserved field (R field).

[0345] Figure 9B illustrates an example structure of this application embodiment with a newly added indicator field in the original MAC subheader. As shown in Figure 9B, the MAC subheader of the MAC sub-PDU for successRAR includes the E field, T1 field, T2 field, S field, C field (corresponding to the aforementioned second OCC indicator field), and L field (corresponding to the aforementioned length indicator field). Optionally, the MAC subheader also includes a reserved field (R field). The functions of the E field, T1 field, T2 field, and S field can be found in the descriptions in related technologies, and will not be repeated here.

[0346] As mentioned earlier, when the second message is sent as a MAC PDU message, the MAC PDU message may also include a MAC sub-PDU for rollback. The following describes the implementation of the MAC sub-PDU for rollback in scenario 3.

[0347] Optionally, the MAC subheader of the MAC subPDU used for rollback includes the first OCC indication field; the first OCC indication field is used to indicate the sixth OCC sequence, which represents the OCC sequence used by the UE performing the rollback operation.

[0348] Figures 10A and 10B respectively show example structural diagrams of the MAC sub-header of the MAC sub-PDU for rollback in case 3. As shown in Figure 10A, the MAC sub-header of the MAC sub-PDU for rollback in this embodiment of the application includes a C field. Optionally, the MAC sub-header also includes a reserved field (R field).

[0349] Figure 10B illustrates an example structure of this application embodiment with a newly added indicator field in the original MAC subheader. As shown in Figure 10B, the MAC subheader of the MAC subPDU used for rollback includes the E field, T1 field, T2 field, S field, and C field. Optionally, the MAC subheader also includes a reserved field (R field).

[0350] For example, when the first UE decodes the MAC sub-PDU used for fallback, it can determine whether the sixth OCC sequence indicated by the first OCC indicator field in the corresponding MAC sub-header is the same as the OCC sequence it used to send the first message. If the OCC sequence used by the first UE to send the first message is the same as the sixth OCC sequence, a fallback operation is performed, for example, falling back to the four-step random access procedure. If the OCC sequence used by the first UE to send the first message is different from the sixth OCC sequence, it is determined that it is unrelated to the MAC sub-PDU used for fallback.

[0351] As mentioned earlier, when the second message is sent as a MAC PDU message, the MAC PDU message may also include a MAC sub-PDU for backoff. The following describes the implementation of the MAC sub-PDU for backoff in scenario 3.

[0352] Optionally, the MAC subheader of the MAC sub-PDU used for backoff includes the third OCC indication field; the third OCC indication field is used to indicate the ninth OCC sequence, which represents the OCC sequence used by the UE performing the backoff operation.

[0353] Figures 10C and 10D respectively show example structural diagrams of the MAC subheader for the MAC sub-PDU used for backoff in Case 3. As shown in Figure 10C, the MAC subheader of the MAC sub-PDU used for backoff in this embodiment of the application includes a C field. Optionally, the MAC subheader also includes a reserved field (R field).

[0354] Figure 10D illustrates an example structure of this application embodiment with an added indicator field in the original MAC subheader. As shown in Figure 10D, the MAC subheader for the MAC subPDU used for backoff includes the E field, T1 field, T2 field, S field, and C field. Optionally, the MAC subheader also includes a reserved field (R field).

[0355] For example, when the first UE decodes the MAC sub-PDU used for backoff, it can determine whether the ninth OCC sequence indicated by the third OCC indicator field in the corresponding MAC sub-header is the same as the OCC sequence it used to send the first message. If the OCC sequence used by the first UE to send the first message is the same as the ninth OCC sequence, a backoff operation is performed, for example, waiting for a certain period of time before sending the first message. If the OCC sequence used by the first UE to send the first message is different from the ninth OCC sequence, it is determined that it is unrelated to the MAC sub-PDU used for backoff.

[0356] The foregoing described various implementations of reusing the second message. It should be understood that in practical applications, the three scenarios shown above may coexist simultaneously or partially, and no specific limitation is made. It should also be understood that the embodiments of this application do not specifically limit the number of MAC sub-PDUs included in the second message; or, in other words, the embodiments of this application do not specifically limit the number of UEs targeted by the second message, which may depend on the network implementation.

[0357] Before applying the aforementioned second message, the network device can configure multiple UEs to reuse the relevant information of the second message.

[0358] Optionally, prior to step 310, the method further includes:

[0359] In step 300, the network device broadcasts a system message, which is then received by multiple UEs (e.g., the first UE). The system message is used to configure relevant information for a second message multiplexed across multiple UEs.

[0360] This application does not specifically limit the content included in the system messages.

[0361] Optionally, the system message includes one or more of the following: a) information enabling the second message; b) capability information supporting the second message; c) preset conditions for the UE to use the second message as a response to the first message; d) maximum number of attempts, which refers to the maximum number of attempts by the UE to send the first message and the application to respond with the second message; e) multiplexing method of the second message, which includes one or more of the following: multiplexing of the second message when multiple UEs send the first message based on the same time domain location; multiplexing of the second message when multiple UEs send the first message based on the same frequency domain location; multiplexing of the second message when multiple UEs send the first message based on the same time and frequency domain location.

[0362] Regarding the above information a, when the network device is configured with an indication information to enable the reuse of the second message, for UEs that support the first message (or the CB-MSG3 mechanism, or the two-step random access mechanism without preamble and RAR) or support the second message (or the reused MSG4), the UE can receive the second message (or receive the reused MSG4) when the network device sends the second message.

[0363] Regarding information b above, when the network device is configured to support the capability information of the second message, for UEs that support the first message or support the second message (or multiplexed MSG4), the second message can be received when the network device sends the second message.

[0364] Regarding information c above, when the network device is configured with a preset condition that the UE uses the second message as a response to the first message, the UE indicates that it can use the second message (or use the multiplexed MSG4) when the corresponding preset condition is met. This application embodiment does not specifically limit the preset conditions for using the second message.

[0365] Optionally, the preset conditions for the UE to use the second message as a response to the first message include an RSRP threshold condition. In some embodiments, the UE determines whether the RSRP threshold condition is met based on the measured RSRP value; if the RSRP threshold condition is met (e.g., the measured RSRP value is greater than or equal to the configured RSRP threshold), it means that the UE can use MSG4 multiplexing. Further optionally, the UE may indicate to the network device in the first message that the UE has the ability to use multiplexed MSG4.

[0366] It should be understood that this description uses the RSRP threshold condition as an example only, and the embodiments of this application are not limited to this. For example, the RSRP threshold condition can also be replaced with other threshold conditions or threshold conditions corresponding to other measurement indicators.

[0367] Regarding the information d above, the maximum number of attempts can be the maximum number of times the UE sends the first message and the application responds with the second message. For example, during the UE's transmission of CB-MSG3, if the number of times the UE sends CB-MSG3 reaches the maximum number of attempts, and the number of times the application reuses MSG4 reaches the maximum number of attempts; if the UE fails to compete, it will fall back to the four-step random access method or fall back to the contention-based advance data transmission (RACH-based EDT) method.

[0368] For example, RACH-based EDT includes the Mobile Initiated Early Data Transmission Control Plane (MO-EDT-CP) transmission procedure and the Mobile Initiated Early Data Transmission User Plane (MO-EDT-UP) transmission procedure. For descriptions of the four-step random access method or the contention-based early data transmission (RACH-based EDT) method, please refer to the relevant technical descriptions; for the sake of indirectness, they will not be elaborated upon here.

[0369] As mentioned earlier, using the CB-MSG3 and MSG4 random access mechanisms can improve transmission efficiency and save signaling overhead. However, if the UE fails to access the network using the CB-MSG3 and MSG4 random access mechanisms, a maximum number of attempts can be set to allow the UE to fall back to other random access mechanisms (such as the aforementioned four-step random access), thereby improving the success rate of random access. In other words, network devices can configure a maximum number of attempts to prevent the UE from continuously using the CB-MSG3 and MSG4 random access mechanisms, thus balancing the relationship between transmission efficiency and access success rate.

[0370] Regarding the aforementioned information e, the network device can configure the multiplexing method for the second message. For example, the multiplexing method may include one or more of the following: multiplexing of MSG4 sent by the network device when CB-MSG3 is sent at the same time domain location; multiplexing of MSG4 sent by the network device when CB-MSG3 is sent at the same frequency domain location; or multiplexing of MSG4 sent by the network device when CB-MSG3 is sent at the same time and frequency domain locations. Correspondingly, the UE uses MSG4 according to the multiplexing method indicated by the network device.

[0371] It should be noted that the system message can be implemented in different ways for the three different cases shown above where the first message is sent at the same time domain location and / or frequency domain location.

[0372] For scenario 2 or 3 above, the system message includes one or more of the information a to e shown above. The implementation methods for each piece of information can be found above and will not be repeated here.

[0373] In some embodiments, for case 1 above, the system message includes one or more of the following: information a to e, information f, frequency domain location information of sending the second message; information g, frequency domain set of ways of applying the second message as a response to the first message, and frequency domain location information of the second message in the frequency domain set.

[0374] For the aforementioned information f, the network device configures the frequency domain location information (such as carrier information and / or index information) for sending the second message, enabling the UE to listen for or receive the second message at the corresponding frequency domain location, thereby improving transmission efficiency.

[0375] Optionally, when a second message indicating network indication for multiplexing at the same time domain location is configured, the frequency domain location information and / or carrier information sent in the second message, such as at frequency point f0, or the center frequency point, or other specified frequency points, or PRB index 0, or other PRB indices, or carrier carrier#0, or anchor carrier, or center carrier carrier, or other specified carriers, or subcarriers; accordingly, the UE will listen for the second message on the corresponding frequency point / carrier according to the frequency point information and / or carrier information indicated by the network device.

[0376] For the aforementioned information g, the network device configures a frequency domain set that can apply the second message and indicates the frequency domain location information for sending the second message in the frequency domain set.

[0377] Optionally, when the network device is configured with a reusable set of frequency domain locations or a set of carriers set_i, and indicates the frequency domain location information for the second message to be sent corresponding to each set of frequency domain locations / carriers set_i, the UE will determine the frequency point / carrier on which to listen for the second message based on the frequency domain / carrier used by itself to send the first message and the set of frequency domains / carriers configured in the configuration information.

[0378] For example, as shown in Figure 11, the network device configures the UE to transmit CB-MSG3 and apply multiplexing MSG4 on frequency domain sets {f0,f1,f2} and {f3,f4,f5}, and indicates the frequency domain location information for multiplexing MSG4 transmission respectively. The network device instructs the UE that transmits CB-MSG3 and applies multiplexing MSG4 on {f0,f1,f2} to listen for MSG4 at frequency domain location f1; and instructs the UE that transmits CB-MSG3 and applies multiplexing MSG4 on {f3,f4,f5} to listen for MSG4 at frequency domain location f4. Accordingly, a UE that transmits CB-MSG3 at any frequency domain location in {f0,f1,f2} can listen for MSG4 at frequency domain location f1; and a UE that transmits CB-MSG3 at any frequency domain location in {f3,f4,f5} can listen for MSG4 at frequency domain location f4.

[0379] For example, the network device configures the UE to transmit CB-MSG3 and apply multiplexing MSG4 on frequency domain sets {PRB0,PRB1,PRB2} and {PRB3,PRB4,PRB5}, and indicates the frequency domain location information for multiplexing MSG4 transmission respectively. The network device instructs the UE transmitting CB-MSG3 and applying multiplexing MSG4 on {PRB0,PRB1,PRB2} to listen for MSG4 at the PRB 1 frequency domain location; and instructs the UE transmitting CB-MSG3 and applying multiplexing MSG4 on {PRB3,PRB4,PRB5} to listen for MSG4 at the PRB 4 frequency domain location. Accordingly, a UE that transmits CB-MSG3 at any frequency domain position in {PRB0, PRB1, PRB2} can listen for MSG4 at the PRB1 frequency domain position; a UE that transmits CB-MSG3 at any frequency domain position in {PRB3, PRB4, PRB5} can listen for MSG4 at the PRB4 frequency domain position.

[0380] For example, the network device configures a UE to transmit CB-MSG3 and apply multiplexing MSG4 on carrier sets {C0, C1, C2} and {C3, C4, C5}, and indicates the frequency domain location information for MSG4 transmission respectively. The network device instructs a UE that transmits CB-MSG3 and applies multiplexing MSG4 on carrier sets {C0, C1, C2} to listen for MSG4 on carrier C0; and instructs a UE that transmits CB-MSG3 and applies multiplexing MSG4 on carrier sets {C3, C4, C5} to listen for MSG4 on carrier C4. Accordingly, a UE that transmits CB-MSG3 at any carrier position in {C0, C1, C2} can listen for MSG4 on carrier C0; a UE that transmits CB-MSG3 at any carrier position in {C3, C4, C5} can listen for MSG4 on carrier C4.

[0381] It should be understood that the above examples regarding frequency domain sets or carrier sets are merely illustrative descriptions, and the embodiments of this application are not limited thereto.

[0382] It should also be understood that the aforementioned information f and information g are optional. Alternatively, the UE may listen for the second message on a default or predefined frequency / carrier. Alternatively, the UE may determine the frequency / carrier to listen for MSG4 based on time-domain information, such as the frequency / carrier for listening to MSG4 being: SFN mod H, where SFN is the subframe number, mod is the modulo operation, and H can be the number of frequency points or the number of carriers.

[0383] It should be noted that the above description is based on the example of a network device configuring the relevant information for multiplexing the second message through system messages, and the embodiments of this application are not limited thereto. Alternatively, the relevant information (information a to information e, information f and information g) included in the above system messages for configuring multiple UEs to multiplex the second message may be partially or entirely predefined by the protocol.

[0384] To clarify, the specific implementation of "predefined" can include any of the following: protocol predefined, manufacturer-specified, defined by the communication equipment, pre-installed in the communication equipment at the time of manufacture, or agreed upon in advance by other agreed methods.

[0385] Furthermore, after receiving or reading the second message, the UE can send a feedback message to the network device. The feedback message is a response to the second message. The network device can configure resources for the UE to transmit the feedback message. The HARQ feedback methods for the aforementioned three scenarios are described below.

[0386] Regarding scenario 1 above, the network device indicates the HARQ resource for the second message to the UE via a system message, DCI, or a second message. Correspondingly, the UE sends a HARQ for the second message to the network device based on the HARQ resource indicated by the network device. These will be described separately below.

[0387] In some embodiments, the network device carries first indication information in the SIB message, which is used to indicate HARQ resources in response to the second message feedback.

[0388] For example, the network device instructs the UE to send HARQ feedback on resources in the frequency domain where the first message is transmitted, or instructs the UE to send HARQ feedback on resources on the carrier where the first message is transmitted, using first indication information in the SIB. Accordingly, the UE sends HARQ feedback for the second message to the network device on the frequency domain resources where the first message is transmitted.

[0389] In some embodiments, the network device carries second indication information in the MAC sub-PDU (e.g., a MAC sub-PDU for carrying contention results; or a MAC SDU) or in the padding field of the second message. This second indication information is used to indicate the HARQ resource responded to in the second message. For example, the MAC sub-PDU for carrying contention results is Success RAR / contention resolution MAC CE.

[0390] For example, the network device may instruct the UE to send HARQ feedback on resources in the frequency domain where the first message is sent by adding second indication information to the Success RAR / contention resolution MAC CE or MAC SDU, or instruct the UE to send HARQ feedback on resources in the carrier where the first message is sent, or instruct the UE to send HARQ feedback using specific carrier information (including carrier index), or instruct the UE to send HARQ feedback using specific frequency domain location (including frequency point or frequency domain identifier).

[0391] In some embodiments, the network device indicates HARQ resources for the second message feedback in the DCI.

[0392] Optionally, the network device instructs the UE to send HARQ feedback using resources in the frequency domain where the first message is sent via DCI, or instructs the UE to send HARQ feedback using resources on the carrier where the first message is sent, or instructs the UE to send HARQ feedback using specific carrier information (including carrier index), or instructs the UE to send HARQ feedback using specific frequency domain locations (including frequency point or frequency domain identifier), or instructs each UE to send HARQ feedback using corresponding resources.

[0393] For example, if the UE sends the first message in frequency domain fx1, then the network device instructs the UE to send HARQ feedback in frequency domain fy1. That is, the frequency domain resources used to transmit HARQ can be different from the frequency domain resources used to send the first message.

[0394] For example, if the UE sends the first message on carrier index x2, then the network device instructs the UE to send a HARQ on carrier index y2 to send a second message in response.

[0395] Optionally, in some embodiments, the instruction to each UE to send HARQ feedback using corresponding resources is provided, that is, for multiple UEs receiving the second message, the resources for HARQ feedback are respectively instructed. For example, UE1 is instructed to use resource 1 to send HARQ feedback, UE2 is instructed to use resource 2 to send HARQ feedback, ..., UEn is instructed to use resource n to send HARQ feedback.

[0396] In response to scenario 2 or 3 above, the network device indicates the HARQ resources for the second message to the UE via the DCI. In some embodiments, the network device sends second indication information, which is carried in the DCI. The second indication information is used to indicate: the time domain resources for HARQ feedback of MSG4 corresponding to the time domain resources used to send the first message;

[0397] For example, the network device instructs via DCI that the UE transmitting the first message at the i-th SFN in the time domain should transmit a HARQ for feedback of the second message on time resource j. Here, i and j can represent different time domain locations.

[0398] It should be understood that the various interactive processes shown above are merely exemplary descriptions, and the embodiments of this application are not limited thereto. In fact, the various embodiments described above can be implemented independently or in reasonable combinations, and the embodiments of this application do not specifically limit them in this regard.

[0399] It should also be understood that the flowcharts or scenario diagrams shown in Figures 1 to 11 are for ease of understanding only and are not intended to limit the embodiments of this application to the examples shown. In fact, those skilled in the art can make equivalent transformations based on the examples in Figures 1 to 11 to obtain more implementation methods.

[0400] The communication method provided by the embodiments of this application has been described in detail above with reference to Figures 1 to 11. The device embodiments of this application will be described in detail below with reference to Figures 12 and 13. It should be understood that the communication device of the embodiments of this application can execute the various communication methods of the foregoing embodiments of this application; that is, the specific working processes of the various products below can be referred to the corresponding processes in the foregoing method embodiments.

[0401] In the embodiments described above, the UE can execute some or all of the steps in each embodiment; the network device can execute some or all of the steps in each embodiment. These steps or operations are merely examples, and the embodiments of this application can also perform other operations or variations of various operations. Furthermore, the steps can be executed in different orders as presented in the embodiments, and it is not necessary to execute all the operations in the embodiments of this application. Moreover, the sequence number of each step 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.

[0402] Figure 12 is a schematic block diagram of a communication device provided in an embodiment of this application. As shown in Figure 12, the communication device 1100 may include a communication module 1120. The communication module 1120 can implement corresponding communication functions, which can be internal communication functions of the communication device 1100 or communication functions between the communication device 1100 and other devices. Optionally, the communication module 1120 may also be referred to as a communication interface or a transceiver module. Optionally, the communication device 1100 further includes a processing module 1110. The processing module 1110 can implement corresponding processing functions.

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

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

[0405] In one possible design, the communication module 1120 is used to send a first message, which is used to transmit uplink data;

[0406] The communication module 1120 is further configured to receive a second message from a network device, the second message containing information on the competition results of multiple UEs, including the first UE.

[0407] Optionally, as an embodiment, the second message is a MAC PDU; the MAC PDU includes one or more of the following:

[0408] The MAC sub-PDU for rollback includes one or more of the following indication fields in its MAC sub-header: a first frequency domain indication field, a first time domain indication field, and a first orthogonal coverage code (OCC) indication field; the first frequency domain indication field indicates the frequency domain information corresponding to the UE performing the rollback operation among the plurality of UEs; the first time domain indication field indicates the time domain information corresponding to the UE performing the rollback operation among the plurality of UEs; and the first OCC indication field indicates the OCC sequence used by the UE performing the rollback operation among the plurality of UEs.

[0409] One or more MAC sub-PDUs are used to carry the contention result, wherein the MAC subheader of each MAC sub-PDU includes one or more of the following: a second frequency domain indication field, a second time domain indication field, a length indication field, and a second OCC indication field; the second frequency domain indication field is used to indicate the frequency domain information corresponding to the UE that successfully competed, or the frequency domain information corresponding to the UE related to the contention result; the second time domain indication field is used to indicate the time domain information corresponding to the UE that successfully competed, or the time domain information corresponding to the UE related to the contention result; the length indication field is used to indicate the length information of the data decoding that the UE needs to skip; the second OCC indication field is used to indicate the OCC sequence adopted by the UE that successfully competed, or the OCC sequence adopted by the UE related to the contention result;

[0410] The MAC sub-PDU for backoff includes one or more of the following indication fields in its MAC sub-header: a third frequency domain indication field, a third time domain indication field, and a third OCC indication field; the third frequency domain indication field indicates the frequency domain information corresponding to the UE performing the backoff operation among the plurality of UEs; the third time domain indication field indicates the time domain information corresponding to the UE performing the backoff operation among the plurality of UEs; and the third OCC indication field indicates the OCC sequence adopted by the UE performing the backoff operation among the plurality of UEs.

[0411] One or more MAC SDUs and / or MAC CEs associated with the one or more MAC sub-PDUs used to carry the competition results.

[0412] Optionally, as an embodiment, the one or more MAC sub-PDUs for carrying the competition result include a first MAC sub-PDU, the MAC sub-header of the first MAC sub-PDU including the second frequency domain indication field and / or the length indication field; the second frequency domain indication field is used to indicate the first frequency domain information;

[0413] The processing module 1110 is configured to determine that the first MAC sub-PDU is related to the first UE when the frequency domain position corresponding to the first frequency domain information is the same as the first frequency domain position, or to determine to decode the first MAC sub-PDU, wherein the first frequency domain position is the frequency domain position where the first UE sends the first message; and to skip decoding the first MAC sub-PDU when the frequency domain position corresponding to the first frequency domain information is different from the first frequency domain position, or to skip data decoding of a first length, wherein the first length is determined based on the length indication field.

[0414] Optionally, as an embodiment, the MAC subheader of the first MAC sub-PDU further includes a second OCC indicator field, which is used to indicate the first OCC sequence;

[0415] The processing module 1110 is used to determine that the first MAC sub-PDU is related to the first UE when the frequency domain position corresponding to the first frequency domain information is the same as the first frequency domain position and the OCC sequence used by the first UE to send the first message is the same as the first OCC sequence, or to determine to decode the first MAC sub-PDU.

[0416] The processing module 1110 is configured to determine that the first MAC sub-PDU is unrelated to the first UE, or to determine not to decode the first MAC sub-PDU, or to determine to skip the decoding of the first MAC sub-PDU, or to determine to skip the data decoding of the first length when the frequency domain position corresponding to the first frequency domain information is different from the first frequency domain position, and / or the OCC sequence used by the first UE to send the first message is different from the first OCC sequence. The first length is determined based on the length indication field.

[0417] Optionally, as an embodiment, the MAC subheader of the MAC subPDU for rollback includes the first frequency domain indication field, which indicates second frequency domain information;

[0418] The processing module 1110 is used to perform a rollback operation when the frequency domain position corresponding to the second frequency domain information is the same as the first frequency domain position;

[0419] The processing module 1110 is used to determine that it is unrelated to the MAC sub-PDU used for rollback when the frequency domain position corresponding to the second frequency domain information is different from the first frequency domain position.

[0420] Optionally, as an embodiment, the MAC subheader of the MAC subPDU for rollback further includes the first OCC indication field;

[0421] The first OCC indication field is used to indicate the second OCC sequence, which represents the OCC sequence used by the UE performing the fallback operation;

[0422] The processing module 1110 is used to perform a rollback operation when the frequency domain position corresponding to the second frequency domain information is the same as the first frequency domain position, and the OCC sequence used by the first UE to send the first message is the same as the second OCC sequence.

[0423] The processing module 1110 is used to determine that it is unrelated to the MAC sub-PDU used for backoff when the frequency domain position corresponding to the second frequency domain information is different from the first frequency domain position, and / or the OCC sequence used by the first UE to send the first message is different from the second OCC sequence.

[0424] Optionally, as an embodiment, the one or more MAC sub-PDUs for carrying the competition result include a second MAC sub-PDU, the MAC sub-header of the second MAC sub-PDU including the second time domain indication field and / or the length indication field; the second time domain indication field is used to indicate the first time domain information;

[0425] The processing module 1110 is used to determine that the second MAC sub-PDU is related to the first UE when the time domain position corresponding to the first time domain information is the same as the first time domain position, or to determine to decode the first MAC sub-PDU, wherein the first time domain position is the time domain position where the first UE sends the first message;

[0426] The processing module 1110 is used to skip decoding of the second MAC sub-PDU or skip data decoding of the second length when the time domain position corresponding to the first time domain information is different from the first time domain position. The second length is determined based on the length indication field.

[0427] Optionally, as an embodiment, when the plurality of UEs send the first message at different time domain positions at the same frequency domain position using an orthogonal coverage code (OCC) sequence, the subheader of the second MAC subPDU further includes a second OCC indication field;

[0428] The second OCC indicator field is used to indicate the third OCC sequence;

[0429] The third OCC sequence represents the OCC sequence corresponding to the UE associated with the second MAC sub-PDU among the plurality of UEs, or the OCC sequence corresponding to the UE that successfully competed among the plurality of UEs;

[0430] The processing module 1110 is used to determine that the second MAC sub-PDU is related to the first UE when the time domain position corresponding to the first time domain information is the same as the first time domain position and the OCC sequence used by the first UE to send the first message is the same as the third OCC sequence, or to determine to decode the second MAC sub-PDU.

[0431] The processing module 1110 is configured to determine that the second MAC sub-PDU is unrelated to the first UE, or skip the decoding of the second MAC sub-PDU, or skip the data decoding of the second length, where the second length is determined based on the length indication field, when the time domain position corresponding to the first time domain information is different from the first time domain position, and / or the OCC sequence used by the first UE to send the first message is different from the third OCC sequence.

[0432] Optionally, as an embodiment, the MAC subheader of the MAC subPDU for rollback includes a first time domain indication field; the first time domain indication field is used to indicate second time domain information;

[0433] The processing module 1110 is used to perform a rollback operation when the time domain position corresponding to the second time domain information is the same as the first time domain position;

[0434] The processing module 1110 is used to determine that it is unrelated to the MAC sub-PDU used for rollback when the time domain position corresponding to the second time domain information is different from the first time domain position.

[0435] Optionally, as an embodiment, when the multiple UEs send the first message at different time domain positions in the same frequency domain position using an orthogonal coverage code (OCC) sequence, the MAC subheader of the MAC subPDU used for backoff further includes the first OCC indication field; the first OCC indication field is used to indicate a fourth OCC sequence, which represents the OCC sequence used by the UE performing the backoff operation among the multiple UEs that send the first message at different time domain positions.

[0436] The processing module 1110 is used to perform a rollback operation when the time domain position corresponding to the second time domain information is the same as the first time domain position, and the OCC sequence used by the first UE to send the first message is the same as the fourth OCC sequence.

[0437] The processing module 1110 is used to determine that it is unrelated to the MAC sub-PDU used for backoff when the time domain position corresponding to the second time domain information is different from the first time domain position, and / or the OCC sequence used by the first UE to send the first message is different from the fourth OCC sequence.

[0438] Optionally, as an embodiment, the one or more MAC sub-PDUs for carrying the competition result include a third MAC sub-PDU, the MAC sub-header of the third MAC sub-PDU including the second OCC indication field and / or the length indication field;

[0439] The second OCC indication field is used to indicate the fifth OCC sequence, which represents the OCC sequence corresponding to the UE associated with the third MAC sub-PDU among multiple UEs that send the first message at the same frequency domain position and the same time domain position, or the OCC sequence corresponding to the UE that successfully competes for the message.

[0440] The processing module 1110 is used to determine, when the OCC sequence used by the first UE to send the first message is the same as the fifth OCC sequence, to determine that it is related to the third MAC sub-PDU, or to determine that the third MAC sub-PDU is decoded.

[0441] The processing module 1110 is configured to determine, when the OCC sequence used by the first UE to send the first message is different from the fifth OCC sequence, whether it is unrelated to the third MAC sub-PDU, or whether it does not decode the third MAC sub-PDU, or whether it skips data decoding of the third length, wherein the third length is determined based on the length indication field.

[0442] Optionally, as an embodiment, the MAC subheader of the MAC subPDU for rollback includes the first OCC indication field; the first OCC indication field is used to indicate a sixth OCC sequence, the sixth OCC sequence representing the OCC sequence used by the UE performing the rollback operation;

[0443] The processing module 1110 is used to perform a rollback operation when the OCC sequence used by the first UE to send the first message is the same as the sixth OCC sequence;

[0444] The processing module 1110 is used to determine that it is unrelated to the MAC sub-PDU used for backoff when the OCC sequence used by the first UE to send the first message is different from the sixth OCC sequence.

[0445] Optionally, as an embodiment, the communication module 1120 is further configured to receive system messages, which are used to configure multiple UEs to reuse the relevant information of the second message.

[0446] Optionally, as an embodiment, the system message includes one or more of the following:

[0447] Enable the information in the second message;

[0448] Information on the capability to support the second message;

[0449] The preset conditions for the UE to use the second message as a response to the first message;

[0450] Maximum number of attempts, which refers to the maximum number of times the UE can send the first message and the application can respond with the second message;

[0451] The multiplexing method of the second message includes one or more of the following: multiplexing of the second message when multiple UEs send the first message based on the same time domain location; multiplexing of the second message when multiple UEs send the first message based on the same frequency domain location; multiplexing of the second message when multiple UEs send the first message based on the same time and frequency domain location.

[0452] Optionally, as an embodiment, the system message further includes one or more of the following: frequency domain information of the network device sending the second message; when the second message is used as a response to the first message, a set of frequency domains that can be used to send the first message and frequency domain information of the network device sending the second message in the set of frequency domains; the communication module 1120 is used to receive the second message from the network device, including: receiving the second message according to the frequency domain information of the second message.

[0453] Optionally, as an embodiment, the communication module 1120 is further configured to receive first indication information, the first indication information being used to indicate HARQ resources for feedback of the second message, the first indication information being carried in any of the following signaling: system message, downlink control information (DCI), MAC SDU in the second message, MAC sub-PDU for contention in the second message, or padding field of the second message;

[0454] The processing module 1110 is further configured to determine the HARQ resource for the second message feedback based on the first indication information, and transmit the HARQ based on the HARQ resource.

[0455] Optionally, as an embodiment, the communication module 1120 is further configured to receive second indication information, the second indication information being used to indicate HARQ resources for the feedback of the second message, the first indication information being carried in the following line control information (DCI);

[0456] The processing module 1110 is further configured to determine the HARQ resource for the second message feedback based on the second indication information, and transmit the HARQ based on the HARQ resource.

[0457] It should be understood that the communication device 1100 may correspond to the UE in Figures 1 to 3 according to the embodiments of this application; the communication device 1100 may include modules or units for executing the methods performed by the UE in Figures 1 to 3. Furthermore, each module and the other operations and / or functions in the communication device 1100 respectively implement the corresponding processes of Figures 1 to 3. In some embodiments, the communication device 1100 may receive the message body structure shown in Figures 4A to 10D and perform corresponding processing, the details of which can be referred to the description of the method embodiments above, and will not be elaborated further.

[0458] It should also be understood that when the communication device 1100 is a UE, the processing module 1110 in the communication device 1100 can be implemented by at least one processor, for example, it can correspond to the processor 1210 in the communication device 1200 shown in FIG. 13. For example, the communication module 1120 can correspond to the communication interface 1220 in the communication device 1200 shown in FIG. 13.

[0459] It should also be understood that when the communication device 1100 is a chip or chip system configured in the UE, the processing module 1110 of the communication device 1100 can be implemented by a processor, microprocessor or integrated circuit integrated on the chip or chip system.

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

[0461] In one possible design, the communication module 1120 is used to receive a first message sent by multiple UEs at the same time domain location and / or the same frequency domain location, the first message being used to transmit uplink data;

[0462] The communication module 1120 is also used to send a second message, which includes information on the competition results of multiple UEs.

[0463] Optionally, as an embodiment, the second message is a MAC PDU; the MAC PDU includes one or more of the following:

[0464] The MAC sub-PDU for rollback includes one or more of the following indication fields in its MAC sub-header: a first frequency domain indication field, a first time domain indication field, and a first orthogonal coverage code (OCC) indication field; the first frequency domain indication field indicates the frequency domain information corresponding to the UE performing the rollback operation among the plurality of UEs; the first time domain indication field indicates the time domain information corresponding to the UE performing the rollback operation among the plurality of UEs; and the first OCC indication field indicates the OCC sequence used by the UE performing the rollback operation among the plurality of UEs.

[0465] One or more MAC sub-PDUs are used to carry the contention result, wherein the MAC subheader of each MAC sub-PDU includes one or more of the following: a second frequency domain indication field, a second time domain indication field, a length indication field, and a second OCC indication field; the second frequency domain indication field is used to indicate the frequency domain information corresponding to the UE that successfully competed, or the frequency domain information corresponding to the UE related to the contention result; the second time domain indication field is used to indicate the time domain information corresponding to the UE that successfully competed, or the time domain information corresponding to the UE related to the contention result; the length indication field is used to indicate the length information of the data decoding that the UE needs to skip; the second OCC indication field is used to indicate the OCC sequence adopted by the UE that successfully competed, or the OCC sequence adopted by the UE related to the contention result;

[0466] The MAC sub-PDU for backoff includes one or more of the following indication fields in its MAC sub-header: a third frequency domain indication field, a third time domain indication field, and a third OCC indication field; the third frequency domain indication field indicates the frequency domain information corresponding to the UE performing the backoff operation among the plurality of UEs; the third time domain indication field indicates the time domain information corresponding to the UE performing the backoff operation among the plurality of UEs; and the third OCC indication field indicates the OCC sequence adopted by the UE performing the backoff operation among the plurality of UEs.

[0467] One or more MAC SDUs and / or MAC CEs associated with the one or more MAC sub-PDUs used to carry the competition results.

[0468] Optionally, as an embodiment, the communication module 1120 is used to receive first messages sent by multiple UEs at the same time domain location and / or the same frequency domain location, including: receiving first messages sent by multiple UEs at different frequency domain locations at the same time domain location;

[0469] Wherein, the one or more MAC sub-PDUs used to carry the competition result include a first MAC sub-PDU, and the MAC sub-header of the first MAC sub-PDU includes the second frequency domain indication field and / or the length indication field;

[0470] The second frequency domain indication field is used to indicate the first frequency domain information.

[0471] Optionally, as an embodiment, when the plurality of UEs send the first message using an orthogonal coverage code (OCC) sequence, the MAC subheader of the first MAC subPDU further includes the second OCC indication field, which is used to indicate the first OCC sequence;

[0472] The first OCC sequence represents the OCC sequence corresponding to the UE that successfully competed among the plurality of UEs, or it represents the OCC sequence corresponding to the UE associated with the first MAC sub-PDU among the plurality of UEs.

[0473] Optionally, as an embodiment, the MAC subheader of the MAC subPDU for rollback includes the first frequency domain indication field, which indicates the second frequency domain information.

[0474] Optionally, as an embodiment, when the plurality of UEs send the first message at different frequency domain positions at the same time domain position using an orthogonal coverage code (OCC) sequence, the MAC subheader of the MAC subPDU for backoff further includes the first OCC indication field;

[0475] The first OCC indication field is used to indicate the second OCC sequence, which represents the OCC sequence used by the UE performing the fallback operation.

[0476] Optionally, as an embodiment, the communication module 1120 is used to receive first messages sent by multiple UEs at the same time domain location and / or the same frequency domain location, including: receiving first messages sent by multiple UEs at different time domain locations at the same frequency domain location; wherein, the one or more MAC sub-PDUs used to carry the contention result include a second MAC sub-PDU, and the MAC sub-header of the second MAC sub-PDU includes the second time domain indication field and / or the length indication field; the second time domain indication field is used to indicate the first time domain information.

[0477] Optionally, as an embodiment, when the plurality of UEs send the first message using an orthogonal coverage code (OCC) sequence, the MAC subheader of the second MAC subPDU further includes the second OCC indication field;

[0478] The second OCC indicator field is used to indicate the third OCC sequence;

[0479] The third OCC sequence represents the OCC sequence corresponding to the UE associated with the second MAC sub-PDU among the plurality of UEs, or the OCC sequence corresponding to the UE that successfully competed among the plurality of UEs.

[0480] Optionally, as an embodiment, the MAC subheader of the MAC subPDU for rollback includes the first time domain indication field; the first time domain indication field is used to indicate the second time domain information.

[0481] Optionally, as an embodiment, when the plurality of UEs send the first message using an orthogonal coverage code (OCC) sequence, the MAC subheader of the MAC subPDU used for fallback further includes the first OCC indication field;

[0482] The first OCC indication field is used to indicate the fourth OCC sequence, which represents the OCC sequence used by the UE performing the backoff operation among multiple UEs that send the first message at different time domain locations.

[0483] Optionally, as an embodiment, the communication module 1120 is used to receive first messages sent by multiple UEs at the same time domain location and / or the same frequency domain location, including: receiving first messages sent by multiple UEs at the same frequency domain location and the same time domain location.

[0484] Wherein, the one or more MAC sub-PDUs used to carry the competition result include a third MAC sub-PDU, and the MAC sub-header of the third MAC sub-PDU includes the second OCC indicator field and / or the length indicator field;

[0485] The second OCC indication field is used to indicate the fifth OCC sequence, which represents the OCC sequence corresponding to the UE associated with the fifth MAC sub-PDU among multiple UEs that send the first message at the same frequency domain position and the same time domain position, or the OCC sequence corresponding to the UE that successfully competes for the message.

[0486] Optionally, as an embodiment, the MAC subheader of the MAC subPDU for rollback includes the first OCC indication field; the first OCC indication field is used to indicate a sixth OCC sequence, the sixth OCC sequence representing the OCC sequence used by the UE performing the rollback operation.

[0487] Optionally, as an embodiment, the communication module 1120 is further configured to send system messages, which are used to configure relevant information of the second message multiplexed for the plurality of UEs.

[0488] Optionally, as an embodiment, the system message includes one or more of the following:

[0489] Enable the information in the second message;

[0490] Information on the capability to support the second message;

[0491] The preset conditions for the UE to use the second message as a response to the first message;

[0492] Maximum number of attempts, which refers to the maximum number of times the UE sends the first message and the application responds with the second message;

[0493] The multiplexing method of the second message includes one or more of the following: multiplexing of the second message when multiple UEs send the first message based on the same time domain location; multiplexing of the second message when multiple UEs send the first message based on the same frequency domain location; multiplexing of the second message when multiple UEs send the first message based on the same time and frequency domain location.

[0494] Optionally, as an embodiment, the system message further includes one or more of the following: frequency domain information of the network device sending the second message; when the second message is used as a response to the first message, a set of frequency domains that can be used to send the first message and frequency domain location information of the network device sending the second message in the set of frequency domains.

[0495] Optionally, as an embodiment, the communication module 1120 is further configured to send first indication information, the first indication information being used to indicate HARQ resources for feedback of the second message, the first indication information being carried in any of the following signaling: system message, downlink control information (DCI), MAC SDU in the second message, MAC sub-PDU for contention in the second message, or padding field of the second message.

[0496] Optionally, as an embodiment, the communication module 1120 is further configured to send a second indication information, the second indication information being used to indicate HARQ resources for the feedback of the second message, the first indication information being carried in the following line control information (DCI).

[0497] It should be understood that the communication device 1100 may correspond to the network device in Figures 1 to 3 according to the embodiments of this application; the communication device 1100 may include modules or units for performing the methods performed by the network device in Figures 1 to 3. Furthermore, each module and the other operations and / or functions in the communication device 1100 respectively implement the corresponding processes of Figures 1 to 3. In some embodiments, the communication device 1100 may send the message body structure shown in Figures 4A to 10D, the details of which can be referred to the description of the method embodiments above, and will not be repeated here.

[0498] It should also be understood that when the communication device 1100 is a network device, the processing module 1110 in the communication device 1100 can be implemented by at least one processor, for example, it can correspond to the processor 1210 in the communication device 1200 shown in FIG. 13. For example, the communication module 1120 can correspond to the communication interface 1220 in the communication device 1200 shown in FIG. 13.

[0499] It should also be understood that when the communication device 1100 is a chip or chip system configured in the aforementioned network equipment, the processing module 1110 of the communication device 1100 can be implemented by a processor, microprocessor, or integrated circuit integrated on the chip or chip system.

[0500] Figure 13 is another schematic block diagram of the communication device 1200 provided in an embodiment of this application. The communication device 1200 can be a UE, a network device, or a chip, chip system, or processor that supports the UE or network device in implementing the above methods. The communication device 1200 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.

[0501] As shown in Figure 13, the communication device 1200 may include one or more processors 1210, which may also be referred to as processing units or processing modules, and can implement certain control functions. The processor 1210 may 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 1200 (e.g., a base station, baseband chip, user, user chip), execute software programs, and process data from the software programs.

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

[0503] In another alternative design, the communication device 1200 may include a communication interface 1220 for implementing receiving and transmitting functions. For example, the communication interface 1220 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.

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

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

[0506] Optionally, if the communication device 1200 includes a processor 1210, a communication interface 1220, and a memory 1230, the processor 1210, the communication interface 1220, and the memory 1230 communicate with each other through internal connection paths.

[0507] Optionally, the memory 1230 may include read-only memory and random access memory, and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. The memory 1230 may be a separate device or integrated into the processor 1210.

[0508] In one implementation, the communication device 1200 may correspond to the UE in the above method embodiments and may be used to execute various steps and / or processes performed by the UE in the above method embodiments. The processor 1210 may be used to execute instructions stored in the memory 1230, and when the processor 1210 executes the instructions stored in the memory, the processor 1210 is used to execute various steps and / or processes of the above method embodiments corresponding to the UE.

[0509] In another implementation, the communication device 1200 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 1210 may be used to execute instructions stored in the memory 1230, and when the processor 1210 executes the instructions stored in the memory, the processor 1210 is used to execute the various steps and / or processes of the above method embodiments corresponding to the network device.

[0510] Optionally, the communication interface 1220 is a transceiver, which may include a transmitter and a receiver. The transceiver may further include an antenna, and the number of antennas may be one or more. The processor 1210 and memory 1230, along with the communication interface 1220, may be devices integrated on different chips. For example, the processor 1210 and memory 1230 may be integrated in a baseband chip, and the communication interface 1220 may be integrated in a radio frequency chip. Alternatively, the processor 1210, memory 1230, and communication interface 1220 may be devices integrated on the same chip. This application does not limit this.

[0511] This application also provides a processing apparatus, including a processor and an interface; the processor is used to execute the communication method in any of the above method embodiments.

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

[0513] In implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software. The steps of the method disclosed in the embodiments of this application can be directly implemented by a hardware processor, or 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 omitted here.

[0514] It should be noted that the processor in the embodiments of this application can be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method embodiments can be completed by the integrated logic circuitry in the processor's hardware or by instructions in software form. The processor can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied as being executed by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located 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 the information in the memory and, in conjunction with its hardware, completes the steps of the above methods.

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

[0516] According to the method provided in the embodiments of this application, this application also provides a chip system, which includes one or more processors for calling and executing instructions stored in memory, thereby causing the method described in the embodiments of this application to be executed. The chip system may be composed of chips or may include chips and other discrete devices.

[0517] The chip system may include input circuits or interfaces for transmitting information or data, and output circuits or interfaces for receiving information or data.

[0518] According to the method provided in the embodiments of this application, this application also provides a communication system, which includes the aforementioned UE and network device.

[0519] Optionally, the communication system may also include other devices that communicate with the UE. Optionally, the communication system may also include other devices that communicate with network devices.

[0520] According to the method provided in the embodiments of this application, this application also provides a computer program product, which includes: computer program code, which, when run on a computer, causes the computer to execute the various steps or processes performed by the UE or network device in any of the foregoing method embodiments.

[0521] According to the method provided in the embodiments of this application, this application also provides a computer-readable storage medium storing program code, which, when run on a computer, causes the computer to execute the various steps or processes performed by the UE or network device in any of the foregoing method embodiments.

[0522] The computer-readable storage medium can be volatile memory or non-volatile memory, or it can 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).

[0523] The above-described device and method embodiments are completely corresponding, with corresponding modules or units performing corresponding steps. For example, a communication unit or communication interface performs the receiving or sending steps in the method embodiment, while other steps besides sending and receiving can be performed by a processing unit or processor.

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

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

[0526] Furthermore, the terms "system" and "network" are often used interchangeably in this paper. The term "and / or" in this paper merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. Additionally, the character " / " in this paper generally indicates that the preceding and following related objects have an "or" relationship. For example, A / B can represent A or B.

[0527] In the embodiments of this application, the terms "information," "signal," "message," "channel," and "signaling" may sometimes be used interchangeably. It should be noted that, without emphasizing the distinction between them, their intended meanings are consistent. Similarly, the terms "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing the distinction between them, their intended meanings are consistent.

[0528] The terms (or numbers) "first," "second," etc., appearing in the embodiments of this application are for descriptive purposes only, that is, only to distinguish different objects, such as different "messages," etc., and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, features defined with "first," "second," etc., may explicitly or implicitly include one or more features. In the description of the embodiments of this application, "at least one (item)" refers to one or more. "Multiple" means two or more. "At least one (item) below" or similar expressions refer to any combination of these items, including any combination of a single (item) or a plurality of (items).

[0529] For example, expressions like "the item includes at least one of the following: A, B, and C" appearing in the embodiments of this application generally mean, unless otherwise specified, that the item can be any one of the following: A; B; C; A and B; A and C; B and C; A, B and C; A and A; A, A and A; A, A and B; A, A and C, A, B and B; A, C and C; B and B, B, B and B, B, B and C, C and C; C, C and C, and other combinations of A, B, and C. The above uses three elements, A, B, and C, as examples to illustrate the possible entries for the item. When expressed as "the item includes at least one of the following: A, B, ..., and X," that is, when the expression contains more elements, then the applicable entries for the item can also be obtained according to the aforementioned rules.

[0530] 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 for data transmission, characterized in that, Applied to network devices, the method includes: Receive a first message sent by multiple UEs at the same time domain location and / or the same frequency domain location, the first message being used to transmit uplink data; A second message is sent, which includes information on the competition results of multiple UEs.

2. The method according to claim 1, characterized in that, The second message is a Media Access Control (MAC) Protocol Data Unit (PDU); the MAC PDU includes one or more of the following: The MAC sub-PDU for rollback includes one or more of the following indication fields in its MAC sub-header: a first frequency domain indication field, a first time domain indication field, and a first orthogonal coverage code (OCC) indication field; the first frequency domain indication field indicates the frequency domain information corresponding to the UE performing the rollback operation among the plurality of UEs; the first time domain indication field indicates the time domain information corresponding to the UE performing the rollback operation among the plurality of UEs; and the first OCC indication field indicates the OCC sequence used by the UE performing the rollback operation among the plurality of UEs. One or more MAC sub-PDUs are used to carry the contention result, wherein the MAC subheader of each MAC sub-PDU includes one or more of the following: a second frequency domain indication field, a second time domain indication field, a length indication field, and a second OCC indication field; the second frequency domain indication field is used to indicate the frequency domain information corresponding to the UE that successfully competed, or the frequency domain information corresponding to the UE related to the contention result; the second time domain indication field is used to indicate the time domain information corresponding to the UE that successfully competed, or the time domain information corresponding to the UE related to the contention result; the length indication field is used to indicate the length information of the data decoding that the UE needs to skip; the second OCC indication field is used to indicate the OCC sequence adopted by the UE that successfully competed, or the OCC sequence adopted by the UE related to the contention result; The MAC sub-PDU for backoff includes one or more of the following indication fields in its MAC sub-header: a third frequency domain indication field, a third time domain indication field, and a third OCC indication field; the third frequency domain indication field indicates the frequency domain information corresponding to the UE performing the backoff operation among the plurality of UEs; the third time domain indication field indicates the time domain information corresponding to the UE performing the backoff operation among the plurality of UEs; and the third OCC indication field indicates the OCC sequence adopted by the UE performing the backoff operation among the plurality of UEs. One or more MAC Service Data Units (SDUs) and / or MAC CEs are associated with the one or more MAC sub-PDUs used to carry the competition results.

3. The method according to claim 2, characterized in that, The step of receiving the first message sent by multiple UEs at the same time domain location and / or the same frequency domain location includes: receiving the first message sent by multiple UEs at different frequency domain locations at the same time domain location; Wherein, the one or more MAC sub-PDUs used to carry the competition result include a first MAC sub-PDU, and the MAC sub-header of the first MAC sub-PDU includes the second frequency domain indication field and / or the length indication field; The second frequency domain indication field is used to indicate the first frequency domain information.

4. The method according to claim 3, characterized in that, When the plurality of UEs send the first message using an orthogonal coverage code (OCC) sequence, the MAC subheader of the first MAC subPDU further includes the second OCC indication field, which is used to indicate the first OCC sequence. The first OCC sequence represents the OCC sequence corresponding to the UE that successfully competed among the plurality of UEs, or it represents the OCC sequence corresponding to the UE associated with the first MAC sub-PDU among the plurality of UEs.

5. The method according to claim 3 or 4, characterized in that, The MAC subheader of the MAC subPDU used for rollback includes the first frequency domain indication field, which indicates the second frequency domain information.

6. The method according to claim 5, characterized in that, When multiple UEs send the first message at different frequency domain positions at the same time domain position using orthogonal coverage code (OCC) sequences, the MAC subheader of the MAC subPDU used for fallback also includes the first OCC indication field; The first OCC indication field is used to indicate the second OCC sequence, which represents the OCC sequence used by the UE performing the fallback operation.

7. The method according to claim 2, characterized in that, The step of receiving the first message sent by multiple UEs at the same time domain location and / or the same frequency domain location includes: receiving the first message sent by multiple UEs at different time domain locations at the same frequency domain location; Wherein, the one or more MAC sub-PDUs used to carry the competition result include a second MAC sub-PDU, and the MAC sub-header of the second MAC sub-PDU includes the second time domain indication field and / or the length indication field; The second time-domain indication field is used to indicate the first time-domain information.

8. The method of claim 7, wherein, When the plurality of UEs send the first message using an orthogonal coverage code (OCC) sequence, the MAC subheader of the second MAC subPDU also includes the second OCC indication field; The second OCC indicator field is used to indicate the third OCC sequence; The third OCC sequence represents the OCC sequence corresponding to the UE associated with the second MAC sub-PDU among the plurality of UEs, or the OCC sequence corresponding to the UE that successfully competed among the plurality of UEs.

9. The method according to claim 7 or 8, characterized in that, The MAC subheader of the MAC subPDU used for rollback includes the first time domain indication field; the first time domain indication field is used to indicate the second time domain information.

10. The method according to claim 9, characterized in that, When the plurality of UEs send the first message using an orthogonal coverage code (OCC) sequence, the MAC subheader of the MAC subPDU used for fallback also includes the first OCC indication field; The first OCC indication field is used to indicate the fourth OCC sequence, which represents the OCC sequence used by the UE performing the backoff operation among multiple UEs that send the first message at different time domain locations.

11. The method according to claim 2, characterized in that, The step of receiving the first message sent by multiple UEs at the same time domain location and / or the same frequency domain location includes: receiving the first message sent by multiple UEs at the same frequency domain location and the same time domain location. Wherein, the one or more MAC sub-PDUs used to carry the competition result include a third MAC sub-PDU, and the MAC sub-header of the third MAC sub-PDU includes the second OCC indicator field and / or the length indicator field; The second OCC indication field is used to indicate the fifth OCC sequence, which represents the OCC sequence corresponding to the UE associated with the fifth MAC sub-PDU among multiple UEs that send the first message at the same frequency domain position and the same time domain position, or the OCC sequence corresponding to the UE that successfully competes for the message.

12. The method according to claim 11, characterized in that, The MAC subheader of the MAC subPDU used for rollback includes the first OCC indication field; the first OCC indication field is used to indicate the sixth OCC sequence, which represents the OCC sequence used by the UE performing the rollback operation.

13. The method according to any one of claims 1 to 12, characterized in that, Before receiving the first messages sent by multiple UEs at the same time domain location and / or the same frequency domain location, the method further includes: Send a system message, which is used to configure the relevant information of the second message for multiplexing for the multiple UEs.

14. The method according to claim 13, characterized in that, The system message includes one or more of the following: Enable the information in the second message; Information on the capability to support the second message; The preset conditions for the UE to use the second message as a response to the first message; Maximum number of attempts, which refers to the maximum number of times the UE sends the first message and the application responds with the second message; The multiplexing method of the second message includes one or more of the following: multiplexing of the second message when the multiple UEs send the first message based on the same time domain location; Multiplexing of the second message when the multiple UEs send the first message based on the same frequency domain location; Multiplexing of the second message when the multiple UEs send the first message based on the same time-frequency domain location.

15. The method according to claim 13 or 14, characterized in that, The system message also includes one or more of the following: frequency domain information of the network device sending the second message; when the second message is used as a response to the first message, the set of frequency domains that can be used to send the first message and the frequency domain location information of the network device sending the second message in the set of frequency domains.

16. A method for data transmission, characterized in that, Applied to a first user equipment (UE), the method includes: Send a first message, which is used to transmit uplink data; A second message is received from a network device, the second message containing information on the competition results of multiple UEs, including the first UE.

17. The method according to claim 16, characterized in that, The second message is a MAC PDU; the MAC PDU includes one or more of the following: The MAC sub-PDU for rollback includes one or more of the following indication fields in its MAC sub-header: a first frequency domain indication field, a first time domain indication field, and a first orthogonal coverage code (OCC) indication field; the first frequency domain indication field indicates the frequency domain information corresponding to the UE performing the rollback operation among the plurality of UEs; the first time domain indication field indicates the time domain information corresponding to the UE performing the rollback operation among the plurality of UEs; and the first OCC indication field indicates the OCC sequence used by the UE performing the rollback operation among the plurality of UEs. One or more MAC sub-PDUs are used to carry the contention result, wherein the MAC subheader of each MAC sub-PDU includes one or more of the following: a second frequency domain indication field, a second time domain indication field, a length indication field, and a second OCC indication field; the second frequency domain indication field is used to indicate the frequency domain information corresponding to the UE that successfully competed, or the frequency domain information corresponding to the UE related to the contention result; the second time domain indication field is used to indicate the time domain information corresponding to the UE that successfully competed, or the time domain information corresponding to the UE related to the contention result; the length indication field is used to indicate the length information of the data decoding that the UE needs to skip; the second OCC indication field is used to indicate the OCC sequence adopted by the UE that successfully competed, or the OCC sequence adopted by the UE related to the contention result; The MAC sub-PDU for backoff includes one or more of the following indication fields in its MAC sub-header: a third frequency domain indication field, a third time domain indication field, and a third OCC indication field; the third frequency domain indication field indicates the frequency domain information corresponding to the UE performing the backoff operation among the plurality of UEs; the third time domain indication field indicates the time domain information corresponding to the UE performing the backoff operation among the plurality of UEs; and the third OCC indication field indicates the OCC sequence adopted by the UE performing the backoff operation among the plurality of UEs. One or more MAC SDUs and / or MAC CEs are associated with the one or more MAC sub-PDUs used to carry the competition results.

18. The method according to claim 17, characterized in that, The one or more MAC sub-PDUs used to carry the competition result include a first MAC sub-PDU, the MAC sub-header of the first MAC sub-PDU including the second frequency domain indication field and / or the length indication field; The second frequency domain indication field is used to indicate the first frequency domain information; The method further includes: If the frequency domain position corresponding to the first frequency domain information is the same as the first frequency domain position, it is determined that the first MAC sub-PDU is related to the first UE, or it is determined that the first MAC sub-PDU is decoded, wherein the first frequency domain position is the frequency domain position where the first UE sends the first message; If the frequency domain position corresponding to the first frequency domain information is different from the first frequency domain position, skip the decoding of the first MAC sub-PDU, or skip the data decoding of the first length, where the first length is determined based on the length indication field.

19. The method according to claim 18, characterized in that, The MAC subheader of the first MAC sub-PDU also includes a second OCC indicator field, which is used to indicate the first OCC sequence; The method further includes: If the frequency domain position corresponding to the first frequency domain information is the same as the first frequency domain position, and the OCC sequence used by the first UE to send the first message is the same as the first OCC sequence, then it is determined that the first MAC sub-PDU is related to the first UE, or it is determined that the first MAC sub-PDU is decoded. If the frequency domain position corresponding to the first frequency domain information is different from the first frequency domain position, and / or the OCC sequence used by the first UE to send the first message is different from the first OCC sequence, it is determined that the first MAC sub-PDU is not related to the first UE, or it is determined that the first MAC sub-PDU is not decoded, or it is determined that the decoding of the first MAC sub-PDU is skipped, or it is determined that the data decoding of the first length is skipped, wherein the first length is determined based on the length indication field.

20. The method according to claim 18 or 19, characterized in that, The MAC subheader of the MAC subPDU used for rollback includes the first frequency domain indication field, which indicates the second frequency domain information. The method further includes: If the frequency domain position corresponding to the second frequency domain information is the same as the first frequency domain position, a rollback operation is performed. If the frequency domain position corresponding to the second frequency domain information is different from the first frequency domain position, it is determined that it is unrelated to the MAC sub-PDU used for rollback.

21. The method according to claim 20, characterized in that, The MAC subheader of the MAC subPDU used for rollback also includes the first OCC indicator field; The first OCC indication field is used to indicate the second OCC sequence, which represents the OCC sequence used by the UE performing the fallback operation; The method further includes: If the frequency domain position corresponding to the second frequency domain information is the same as the first frequency domain position, and the OCC sequence used by the first UE to send the first message is the same as the second OCC sequence, then a rollback operation is performed. If the frequency domain position corresponding to the second frequency domain information is different from the first frequency domain position, and / or the OCC sequence used by the first UE to send the first message is different from the second OCC sequence, it is determined that it is unrelated to the MAC sub-PDU used for backoff.

22. The method according to claim 17, characterized in that, The one or more MAC sub-PDUs used to carry the competition result include a second MAC sub-PDU, the MAC sub-header of the second MAC sub-PDU including the second time domain indication field and / or the length indication field; The second time-domain indication field is used to indicate the first time-domain information; The method further includes: If the time domain position corresponding to the first time domain information is the same as the first time domain position, it is determined that the second MAC sub-PDU is related to the first UE, or it is determined that the first MAC sub-PDU is decoded, wherein the first time domain position is the time domain position where the first UE sends the first message; If the time domain position corresponding to the first time domain information is different from the first time domain position, skip the decoding of the second MAC sub-PDU, or skip the data decoding of the second length, which is determined based on the length indication field.

23. The method according to claim 22, characterized in that, When the multiple UEs send the first message at different time domain positions in the same frequency domain position using the orthogonal coverage code (OCC) sequence, the subheader of the second MAC subPDU also includes a second OCC indication field; The second OCC indicator field is used to indicate the third OCC sequence; The third OCC sequence represents the OCC sequence corresponding to the UE associated with the second MAC sub-PDU among the plurality of UEs, or the OCC sequence corresponding to the UE that successfully competed among the plurality of UEs; The method further includes: If the time domain position corresponding to the first time domain information is the same as the first time domain position, and the OCC sequence used by the first UE to send the first message is the same as the third OCC sequence, then it is determined that the second MAC sub-PDU is related to the first UE, or it is determined that the second MAC sub-PDU is decoded. If the time domain position corresponding to the first time domain information is different from the first time domain position, and / or the OCC sequence used by the first UE to send the first message is different from the third OCC sequence, it is determined that the second MAC sub-PDU is not related to the first UE, or the decoding of the second MAC sub-PDU is skipped, or the data decoding of the second length is skipped, the second length being determined based on the length indication field.

24. The method according to claim 22 or 23, characterized in that, The MAC subheader of the MAC subPDU used for rollback includes a first time domain indication field; the first time domain indication field is used to indicate second time domain information; The method further includes: If the time domain position corresponding to the second time domain information is the same as the first time domain position, a rollback operation is performed; If the time domain position corresponding to the second time domain information is different from the first time domain position, it is determined that it is unrelated to the MAC sub-PDU used for rollback.

25. The method of claim 24, wherein, When multiple UEs send the first message at different time domain positions in the same frequency domain position using an orthogonal coverage code (OCC) sequence, the MAC subheader of the MAC subPDU used for fallback also includes the first OCC indication field; The first OCC indication field is used to indicate the fourth OCC sequence, which represents the OCC sequence used by the UE performing the backoff operation among multiple UEs that send the first message at different time domain locations; The method further includes: If the time domain position corresponding to the second time domain information is the same as the first time domain position, and the OCC sequence used by the first UE to send the first message is the same as the fourth OCC sequence, a rollback operation is performed. If the time domain position corresponding to the second time domain information is different from the first time domain position, and / or the OCC sequence used by the first UE to send the first message is different from the fourth OCC sequence, it is determined that it is unrelated to the MAC sub-PDU used for backoff.

26. The method according to claim 17, characterized in that, The one or more MAC sub-PDUs used to carry the competition result include a third MAC sub-PDU, the MAC sub-header of which includes the second OCC indication field and / or the length indication field; The second OCC indication field is used to indicate the fifth OCC sequence, which represents the OCC sequence corresponding to the UE associated with the third MAC sub-PDU among multiple UEs that send the first message at the same frequency domain position and the same time domain position, or the OCC sequence corresponding to the UE that successfully competes for the message. The method further includes: If the OCC sequence used by the first UE to send the first message is the same as the fifth OCC sequence, it is determined that it is related to the third MAC sub-PDU, or it is determined that the third MAC sub-PDU is decoded; If the OCC sequence used by the first UE to send the first message is different from the fifth OCC sequence, it is determined that it is unrelated to the third MAC sub-PDU, or it is determined that the third MAC sub-PDU will not be decoded, or the data decoding of the third length is skipped, the third length being determined based on the length indication field.

27. The method according to claim 26, characterized in that, The MAC subheader of the MAC subPDU used for fallback includes the first OCC indication field; the first OCC indication field is used to indicate the sixth OCC sequence, the sixth OCC sequence representing the OCC sequence used by the UE performing the fallback operation; The method further includes: If the OCC sequence used by the first UE to send the first message is the same as the sixth OCC sequence, a rollback operation is performed; If the OCC sequence used by the first UE to send the first message is different from the sixth OCC sequence, it is determined that it is unrelated to the MAC sub-PDU used for backoff.

28. The method according to any one of claims 16 to 27, characterized in that, Before sending the first message, the method further includes: Receive a system message, which is used to configure multiple UEs to reuse the relevant information of the second message.

29. The method according to claim 28, characterized in that, The system message includes one or more of the following: Enable the information in the second message; Information on the capability to support the second message; The preset conditions for the UE to use the second message as a response to the first message; Maximum number of attempts, which refers to the maximum number of times the UE can send the first message and the application can respond with the second message; The multiplexing method of the second message includes one or more of the following: when the multiple UEs send the first message based on the same time domain location, the second message is multiplexed; When multiple UEs send the first message based on the same frequency domain location, the second message is multiplexed; when multiple UEs send the first message based on the same time-frequency domain location, the second message is multiplexed.

30. The method according to claim 28 or 29, characterized in that, The system message also includes one or more of the following: frequency domain information of the network device sending the second message; when the second message is used as a response to the first message, a set of frequency domains that can be used to send the first message and frequency domain information of the network device sending the second message in the set of frequency domains; The step of receiving the second message from the network device includes: receiving the second message based on the frequency domain information of the second message.

31. A communication system, characterized in that, It includes multiple user equipment (UE) devices and network devices, wherein the multiple UE devices include at least a first UE; The network device is configured to perform the method of any one of claims 1-15; and the first UE is configured to perform the method of any one of claims 16-30.

32. A communications device, characterized by The apparatus includes at least one processor coupled with a memory for storing programs or instructions, and the processor executes the programs or instructions to cause the apparatus to perform the method of any one of claims 1-15, or to cause the apparatus to perform the method of any one of claims 16-30.

33. A computer readable storage medium having stored thereon a computer program or instructions, characterized in that, The computer programs or instructions, when executed, cause a computer to perform the method of any one of claims 1-15, or to perform the method of any one of claims 16-30.

34. A chip system, characterized in that, The chip system includes one or more processors configured to call and run instructions stored in a memory, so that the method of any one of claims 1-15 is performed, or the method of any one of claims 16-30 is performed.