CN115225223A

CN115225223A - Method and arrangement in a communication node used for wireless communication

Info

Publication number: CN115225223A
Application number: CN202110422003.4A
Authority: CN
Inventors: 于巧玲; 张晓博
Original assignee: Shanghai Langbo Communication Technology Co Ltd
Current assignee: Shanghai Langbo Communication Technology Co Ltd
Priority date: 2021-04-20
Filing date: 2021-04-20
Publication date: 2022-10-21

Abstract

A method and arrangement in a communication node for wireless communication is disclosed. The communication node builds a first MAC PDU; transmitting the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload; the first domain is one of the first MAC subheader except the LCID domain; the first MAC payload is not the first status report. The application provides a method for indicating whether a MAC sub-PDU comprises a first status report or not through a domain in an MAC sub-header.

Description

Method and arrangement in a communication node used for wireless communication

Technical Field

The present application relates to a transmission method and apparatus in a wireless communication system, and more particularly, to a transmission method and apparatus of a MAC PDU.

Background

A MAC (Medium Access Control) PDU (Protocol Data Unit) includes at least one MAC sub-PDU (sub-PDU), where one MAC sub-PDU includes a MAC sub-header (sub-header), and when the MAC sub-PDU carries a MAC SDU (Service Data Unit) or a variable-Length MAC CE (Control Element), the MAC sub-header needs to include a Length (L) Field (Field) indicating the Length of the MAC SDU or the variable-Length MAC CE carried in the MAC sub-PDU, and indicates, through a Format (F) Field, that the Length of the L Field is equal to 1 byte (byte) or 2 bytes.

Disclosure of Invention

In a specific scenario, if the amount of Data to be transmitted is Small, it may happen that the length of the L domain is always equal to 1 byte or approximately equal to 1 byte, such as SDT (Small Data Transmission) or NB-IoT (narrow band Internet of Things) system, and if the F domain is still used to indicate the length of the L domain, it is always or with a high probability set to 0, thereby causing the F domain to lose practical meaning. Therefore, enhancement of the format of the MAC sub-PDU is required.

In view of the above, the present application provides a solution. In the description of the above problem, an NR scenario is taken as an example; the method and the device are also applicable to scenarios such as LTE (Long Term Evolution), NB-IoT (NB-IoT) or V2X (Vehicle-to-Evolution), and achieve technical effects similar to those in NR scenarios. In addition, the adoption of a unified solution for different scenarios also helps to reduce hardware complexity and cost.

As an example, the interpretation of the term (Terminology) in the present application refers to the definitions of the specification protocol TS36 series of 3 GPP.

As an embodiment, the interpretation of terms in the present application refers to the definitions of the specification protocols TS38 series of 3 GPP.

As an embodiment, the interpretation of the terms in the present application refers to the definitions of the 3GPP specification protocol TS37 series.

As an example, the terms in the present application are explained with reference to the definition of the specification protocol of IEEE (Institute of Electrical and Electronics Engineers).

It should be noted that, in the case of no conflict, the embodiments and features in the embodiments in any node of the present application may be applied to any other node. The embodiments and features of the embodiments of the present application may be combined with each other arbitrarily without conflict.

The application discloses a method in a first node used for wireless communication, characterized by comprising:

building a first MAC PDU; transmitting the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and a LCID (Logical Channel ID) field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload;

wherein the first domain is one of the first MAC subheader except for the LCID domain; the first MAC load is not the first status report.

As an embodiment, the problem to be solved by the present application includes: how to reduce the signaling overhead.

As an embodiment, the problem to be solved by the present application includes: how to reuse the existing fields in the MAC subheader.

As an embodiment, the problem to be solved by the present application includes: how to improve the resource utilization efficiency.

It may happen that the length of the L-field is always equal to 1 byte or approximately 1 byte, such as SDT or NB-IoT systems, and if the F-field is still used to indicate the length of the L-field, it is always or with a high probability set to 0, resulting in the F-field losing practical meaning

As an embodiment, the characteristics of the above method include: the values of the existing fields are redefined.

As an embodiment, the characteristics of the above method include: a new MAC subheader is designed.

As an embodiment, the characteristics of the above method include: the first field in the first MAC subheader is used to indicate whether the first MAC subPDU includes a first status report, the first field being one of the first MAC subheader other than the LCID field; the first MAC payload is not the first status report.

As an embodiment, the characteristics of the above method include: one field of the MAC subheader except the LCID field indicates whether the first status report exists in the MAC PDU.

As an embodiment, the characteristics of the above method include: the first MAC subheader includes other fields in addition to the first field and the LCID field.

As an embodiment, the characteristics of the above method include: only the first domain and the LCID domain are included in the first MAC subheader.

As an embodiment, the characteristics of the above method include: the first MAC subheader consists of a first field and an LCID field.

As an example, the benefits of the above method include: one MAC subheader is reduced in the MAC PDU.

As an example, the benefits of the above method include: reuse existing domains, avoiding increasing overhead.

According to an aspect of the application, wherein the first status report belongs to the first MAC subheader.

As an embodiment, the characteristics of the above method include: one of the domains other than the LCID domain in the MAC subheader indicates whether a first status report exists in the MAC subheader.

According to one aspect of the present application, the first MAC sub-PDU comprises a second MAC payload, the second MAC payload comprising the first status report.

As an embodiment, the characteristics of the above method include: one of the domains other than the LCID domain in the MAC subheader indicates whether the first status report exists in the second MAC payload.

According to one aspect of the present application, a second field is included in the first MAC subheader, wherein the second field indicates a length of the first MAC payload.

As an embodiment, the characteristics of the above method include: the first MAC subheader comprises a first domain, an LCID domain and a second domain.

As an embodiment, the characteristics of the above method include: the first MAC subheader consists of a first field, an LCID field and a second field.

As an embodiment, the characteristics of the above method include: the first MAC subheader consists of a first domain, an LCID domain, a second domain and a reserved domain.

As an embodiment, the characteristics of the above method include: the first MAC subheader includes a first field, an LCID field, an eLCID (extended Logical Channel ID) field, and a second field.

As an embodiment, the characteristics of the above method include: the first MAC subheader consists of a first domain, an LCID domain, an eLCID domain and a second domain.

As an embodiment, the characteristics of the above method include: the first MAC subheader consists of a first domain, an LCID domain, an eLCID domain, a second domain and a reserved domain.

According to one aspect of the application, the method is characterized by comprising the following steps:

sending a first message; recovering at least a first DRB (Data Radio Bearer) along with the first message; triggering the first status report in response to a first set of conditions being satisfied;

wherein the first message is used for a first RRC (Radio Resource Control) recovery procedure; the first set of conditions includes that the first RRC recovery procedure is being performed and a first data block is in effect, the first data block being associated with the first DRB; the first status report indicates a cache coherency state.

As an embodiment, the characteristics of the above method include: the first status report is for the first RRC recovery procedure.

receiving first signaling used to determine whether the first field is used to indicate whether the first MAC sub-PDU includes a first status report.

The application discloses a method in a second node used for wireless communication, characterized by comprising:

receiving a first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload;

wherein the first MAC PDU is assembled; the first domain is one of the first MAC subheader except the LCID domain; the first MAC payload is not the first status report.

According to an aspect of the present application, wherein the first status report belongs to the first MAC subheader.

receiving a first message;

wherein at least a first DRB is resumed with the first message; in response to a first set of conditions being met, the first status report is triggered; the first message is used for a first RRC recovery procedure; the first set of conditions includes that the first RRC recovery procedure is being performed and a first data block is in effect, the first data block being associated with the first DRB; the first status report indicates a cache coherency state.

transmitting first signaling used to determine whether the first field is used to indicate whether the first MAC sub-PDU includes a first status report.

The present application discloses a first node for wireless communication, comprising:

a first transmitter for constructing a first MAC PDU; transmitting the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload;

wherein the first domain is one of the first MAC subheader except for the LCID domain; the first MAC payload is not the first status report.

The application discloses a second node used for wireless communication, characterized by comprising:

a second receiver receiving the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload;

wherein the first MAC PDU is assembled; the first field is a field of the first MAC subheader other than the LCID field; the first MAC payload is not the first status report.

As an example, compared with the conventional scheme, the method has the following advantages:

-reducing a MAC subheader in the MAC PDU;

reusing the existing domain, avoiding increasing overhead;

avoiding the situation that the new data arrives and the BSR (Buffer Status Report) cannot be triggered in time;

avoiding the situation that the uplink resource cannot accommodate one BSR and its MAC subheader and the BSR is deleted;

improving the efficiency of resource utilization;

reducing the probability of SDT delivery failure due to expiration of a timer during SDT.

Drawings

Other features, objects and advantages of the present application will become more apparent upon reading of the detailed description of the non-limiting embodiments with reference to the following drawings in which:

fig. 1 shows a flow diagram of transmission of a first MAC PDU according to one embodiment of the present application;

FIG. 2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

figure 3 shows a schematic diagram of an embodiment of a radio protocol architecture for the user plane and the control plane according to an embodiment of the present application;

FIG. 4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

FIG. 5 shows a flow diagram of wireless signal transmission according to one embodiment of the present application;

FIG. 6 shows a flow diagram of wireless signal transmission according to another embodiment of the present application;

fig. 7 shows a schematic diagram of a first status report belonging to a first MAC subheader according to an embodiment of the present application;

fig. 8 shows a schematic diagram of a second MAC payload including a first status report according to an embodiment of the application;

fig. 9 illustrates a schematic diagram of a format of a first MAC sub-PDU according to one embodiment of the present application;

fig. 10 illustrates a schematic diagram of a format of a first MAC sub-PDU according to another embodiment of the present application;

fig. 11 is a diagram illustrating a format of a first MAC sub-PDU according to still another embodiment of the present application;

fig. 12 shows a schematic diagram of a first MAC subheader according to a first embodiment of the present application;

fig. 13 shows a schematic diagram of a first MAC subheader according to a second embodiment of the present application;

fig. 14 shows a schematic diagram of a first MAC subheader according to a third embodiment of the present application;

fig. 15 shows a schematic diagram of a first MAC subheader according to a fourth embodiment of the present application;

fig. 16 shows a schematic diagram of a first MAC subheader according to a fifth embodiment of the present application;

fig. 17 shows a schematic diagram of a first MAC subheader according to a sixth embodiment of the present application;

fig. 18 shows a schematic diagram of a first MAC subheader according to a seventh embodiment of the present application;

fig. 19 shows a schematic diagram of a first MAC subheader according to an eighth embodiment of the present application;

figure 20 shows a schematic diagram of a first MAC load and a second MAC load according to an embodiment of the application;

fig. 21 shows a schematic diagram of a first MAC load and a second MAC load according to another embodiment of the present application;

FIG. 22 shows a block diagram of a processing device for use in a first node according to an embodiment of the present application;

figure 23 shows a block diagram of a processing arrangement for use in a second node according to an embodiment of the present application;

fig. 24 shows a schematic diagram of a target domain or a second MAC payload domain according to an embodiment of the present application.

Detailed Description

The technical solutions of the present application will be further described in detail with reference to the accompanying drawings, and it should be noted that the embodiments and features of the embodiments in the present application can be arbitrarily combined with each other without conflict.

Example 1

Embodiment 1 illustrates a flow chart of transmission of a first MAC PDU according to one embodiment of the present application, as shown in fig. 1. In fig. 1, each block represents a step, and it is particularly emphasized that the sequence of the blocks in the figure does not represent a chronological relationship between the represented steps.

In embodiment 1, a first node in the present application builds a first MAC PDU in step 101; transmitting the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload; wherein the first domain is one of the first MAC subheader except for the LCID domain; the first MAC load is not the first status report.

As an embodiment, the meaning that one MAC PDU or one MAC sub-header or one MAC payload or one field includes one parameter includes: the one field indicates the one parameter.

As an embodiment, the meaning that one MAC PDU or one MAC sub-header or one MAC payload or one field includes one parameter includes: the one MAC PDU or one MAC sub-header or one MAC payload or one domain display indicates the one parameter.

As an embodiment, the meaning that one MAC PDU or one MAC sub-header or one MAC payload or one field includes one parameter includes: the one MAC PDU or one MAC sub-header or one MAC payload or one domain implicitly indicates the one parameter.

As an embodiment, the meaning that one MAC PDU or one MAC sub-header or one MAC payload or one field includes one parameter includes: the one MAC PDU or one MAC sub-header or one MAC payload or one field is used to determine the one parameter.

As an embodiment, the meaning that one MAC PDU or one MAC sub-header or one MAC payload or one field includes one parameter includes: the one MAC PDU or one MAC sub-header or one MAC payload or one domain includes the one parameter.

As an embodiment, the meaning that one MAC PDU or one MAC sub-header or one MAC payload or one field includes one parameter includes: the one MAC PDU or one MAC sub-header or one MAC payload or one domain carries the one parameter.

As an embodiment, the meaning that one MAC PDU or one MAC sub-header or one MAC payload or one field includes one parameter includes: the one MAC PDU or one MAC sub-header or one MAC payload or one domain includes another domain, and the one parameter is included in the other domain.

As an embodiment, the first MAC PDU is a Protocol Data Unit (Protocol Data Unit) of a MAC layer.

As an embodiment, the first MAC PDU is one MAC PDU.

As a sub-embodiment of this embodiment, the one MAC PDU is a bit string (a bit string that is byte aligned in length) byte aligned (e.g., 8 bits) in length.

As a sub-embodiment of this embodiment, the leftmost bit of the first row in the bit string is the most significant bit (the most significant bit is the missing most bit of the first line of the bit string of the table), and the rightmost bit of the last row in the bit string is the least significant bit (the least significant bit is the rightmost bit on the last line of the table).

As a sub-embodiment of this embodiment, the bit string is read from left to right (the bit string is to be read from left to right) and in the reading order of the rows (in the reading order of the lines).

As an embodiment, the behavior building the first MAC PDU includes: multiplexing of MAC CE and MAC SDU.

As an embodiment, the behavior building the first MAC PDU includes: logical Channel Prioritization (LCP).

As an embodiment, the behavior building the first MAC PDU includes: selection of logical channels.

As an embodiment, the behavior building the first MAC PDU includes: resource Allocation (Resource Allocation).

As an embodiment, the behavior building the first MAC PDU includes: according to the format of the MAC PDU, a plurality of MAC sub-PDUs are concatenated together.

As an embodiment, the behavior building the first MAC PDU includes: obtaining the first MAC PDU.

As one embodiment, the first MAC PDU is transmitted over an air interface.

As a sub-embodiment of this embodiment, the air interface comprises an interface between two UEs.

As a sub-embodiment of this embodiment, the air interface comprises an interface between two gNBs/eNGs.

As a sub-embodiment of this embodiment, the air interface includes an interface between one UE and one gNB/eNB.

As a sub-embodiment of this embodiment, the air interface comprises an interface between the first node and the second node.

As an embodiment, the phrase that the first MAC PDU comprises a first MAC sub-PDU includes: the first MAC PDU includes one MAC sub-PDU or more MAC sub-PDUs, the first MAC sub-PDU being the one MAC sub-PDU or the first MAC sub-PDU being one of the more MAC sub-PDUs.

As an embodiment, the phrase that the first MAC PDU comprises a first MAC sub-PDU includes: the first MAC PDU includes one MAC sub-PDU, which is the one MAC sub-PDU.

As a sub-embodiment of this embodiment, the first MAC sub-PDU includes only one MAC sub-header.

As a sub-embodiment of this embodiment, the first MAC sub-PDU includes one MAC sub-header and one MAC SDU.

As a sub-embodiment of this embodiment, the first MAC sub-PDU includes one MAC sub-header and one MAC CE.

As a sub-embodiment of this embodiment, the first MAC sub-PDU includes a MAC sub-header and padding (padding).

As an embodiment, the phrase that the first MAC PDU comprises a first MAC sub-PDU includes: the first MAC PDU includes a plurality of MAC sub-PDUs including at least 2 MAC sub-PDUs, the first MAC sub-PDU being one of the plurality of MAC sub-PDUs.

As a sub-embodiment of this embodiment, the first MAC sub-PDU consists of only one MAC sub-header.

As a sub-embodiment of this embodiment, the first MAC sub-PDU consists of one MAC sub-header and one MAC SDU.

As a sub-embodiment of this embodiment, the first MAC sub-PDU consists of one MAC sub-header and one MAC CE.

As a sub-embodiment of this embodiment, the first MAC sub-PDU consists of one MAC sub-header and padding (padding).

As a sub-embodiment of this embodiment, one of the more MAC sub-PDUs except the first MAC sub-PDU consists of only one MAC sub-header.

As a sub-embodiment of this embodiment, one of the plurality of MAC sub-PDUs except for the first MAC sub-PDU is composed of one MAC sub-header and one MAC SDU.

As a sub-embodiment of this embodiment, one of the more MAC sub-PDUs except for the first MAC sub-PDU is composed of one MAC sub-header and one MAC CE.

As a sub-embodiment of this embodiment, one of the more MAC sub-PDUs except the first MAC sub-PDU is composed of one MAC sub-header and padding (padding).

As an embodiment, the first MAC sub-PDU is a first MAC sub-PDU of the first MAC PDUs.

As an embodiment, the first MAC sub-PDU is any one of the first MAC sub-PDUs.

As an embodiment, the first MAC PDU consists of the first MAC sub-PDU.

As an embodiment, the phrase that the first MAC sub-PDU includes a first MAC sub-header includes: the first MAC subheader is a MAC subheader for the first MAC subpdu.

As an embodiment, the phrase that the first MAC sub-PDU includes a first MAC sub-header includes: the first MAC subheader is one of the first MAC subheaders.

As an embodiment, the phrase that the first MAC sub-PDU includes a first MAC sub-header includes: the first MAC subheader belongs to the first MAC subpdu.

As an embodiment, the phrase that the first MAC sub-PDU includes a first MAC sub-header includes: the first MAC subheader indicates the first MAC subpdu.

As an embodiment, the phrase that the first MAC sub-PDU includes a first MAC sub-header includes: the first MAC subheader is used to determine the first MAC subPDU.

As an embodiment, the phrase that the first MAC sub-PDU includes a first MAC sub-header includes: the first MAC sub-PDU carries the first MAC sub-header.

As an embodiment, the first MAC sub-PDU comprises only one MAC sub-header, the one MAC sub-header being the first MAC sub-header.

For one embodiment, the first MAC subheader comprises a MAC subheader.

As an embodiment, the first MAC subheader is a byte aligned (e.g., multiple 8 bits) bit string (a bit string that is byte aligned in length) in length.

As an embodiment, the first MAC subheader is directly placed before the corresponding MAC SDU, or MAC CE or padding (padding) (is placed after the MAC SDU, MAC CE, or padding).

As an embodiment, the first MAC subheader consists of an R (Reserved) field, an F (Format) field, an LCID field, and an L (Length) field; wherein one MAC sub-PDU to which the one MAC sub-header belongs is not one of a MAC CE of a fixed size, or a MAC SDU which is padded or includes a UL CCCH (Common Control Channel).

For one embodiment, the first MAC subheader consists of an R domain, an F domain, an LCID domain, an eLCID domain, and an L domain; wherein one MAC sub-PDU to which the one MAC sub-header belongs is not one of a MAC CE of a fixed size, or a MAC SDU which fills or includes an UL CCCH.

As an embodiment, the first MAC subheader consists of an R field and an LCID field; wherein, one MAC sub-PDU to which the one MAC sub-header belongs includes a MAC CE of a fixed size, or a MAC SDU which is padded or includes an UL (UpLink) CCCH.

For one embodiment, the first MAC subheader consists of an R field, an LCID field, and an eLCID field; wherein, one MAC sub-PDU to which the one MAC sub-header belongs includes a MAC CE of a fixed size, or a MAC SDU which fills or includes UL CCCH.

As an embodiment, the phrase including at least a first field and an LCID field in the first MAC subheader includes: the first domain and the LCID domain are two domains in the first MAC subheader.

As an embodiment, the phrase including at least a first field and an LCID field in the first MAC subheader includes: only the first field and the LCID field are included in the first MAC subheader.

As a sub-embodiment of this embodiment, the first MAC subheader is composed of the first field and the LCID field.

As a sub-embodiment of this embodiment, the first field in the first MAC subheader is placed directly before the LCID field.

As an embodiment, the phrase including at least a first field and an LCID field in the first MAC subheader includes: the first MAC subheader includes other fields in addition to the first field and the LCID field.

As an embodiment, the phrase including at least a first field and an LCID field in the first MAC subheader includes: the first MAC subheader includes at least 3 MAC domains therein, and the first domain and the LCID domain are two of the at least 3 MAC domains.

As a sub-embodiment of this embodiment, the first MAC subheader includes 3 MAC fields therein.

As a sub-embodiment of this embodiment, the first MAC subheader includes 4 MAC fields therein.

As a sub-embodiment of this embodiment, the first MAC subheader includes 5 MAC fields therein.

As a sub-embodiment of this embodiment, the first MAC subheader includes 6 MAC fields therein.

As one embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report includes: the first field in the first MAC subheader indicates whether the first MAC subPDU includes a first status report.

As one embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report includes: the first field in the first MAC subheader is used to determine whether the first MAC subPDU includes a first status report.

As one embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report includes: the first field in the first MAC subheader indicates whether there is one byte in the first MAC subPDU that includes the first status report.

As one embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report includes: the first field in the first MAC subheader indicates that the first MAC subPDU includes the first status report.

As one embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report includes: the first field in the first MAC subheader indicates that the first MAC subPDU does not include the first status report.

As one embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report includes: the first field in the first MAC subheader is used to indicate whether one field is included in the first MAC subPDU, the one field including the first status report.

As one embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report includes: the first MAC sub-PDU includes a field therein, the field being used to indicate the first status report; the first field in the first MAC subheader is used to indicate whether the first status report is included in the first MAC subPDU.

As a sub-embodiment of this embodiment, the setting of the one field to a default value indicates that the first status report is not included in the first MAC sub-PDU.

As a sub-embodiment of this embodiment, the setting of the one field to a specific value indicates that the first status report is included in the first MAC sub-PDU.

As one embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report includes: the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes the first status reporting field in this application, which includes a first status report.

As one embodiment, the first field in the first MAC subheader indicates that the first MAC subpdu includes the first status report used to determine that the first node has at least one more uplink transmission.

As one embodiment, the first field in the first MAC subheader indicates that the first MAC subpdu does not include the first status report used to determine that the first node did not expect uplink transmission.

As an embodiment, only the first MAC sub-PDU of the first MAC PDUs is used for one field indicating whether the first MAC sub-PDU includes a first status report.

As a sub-embodiment of this embodiment, there is no field in the MAC subheader of the other MAC sub-PDU except the first MAC sub-PDU in the first MAC PDU, which is used to indicate whether the first MAC sub-PDU includes the first status report.

As a sub-embodiment of this embodiment, the first MAC sub-PDU is any one of the first MAC sub-PDUs.

As a sub-embodiment of this embodiment, the first MAC sub-PDU is a first MAC sub-PDU of the first MAC PDUs.

As a sub-embodiment of this embodiment, the first status report is only for a logical channel corresponding to the LCID field in the first MAC sub-PDU.

As a sub-embodiment of this embodiment, the first status report is directed to a Logical Channel Group (LCG) to which a Logical Channel corresponding to the LCID field in the first MAC sub-PDU belongs.

As one embodiment, the first field in the MAC subheader of each of the first MAC PDU is used to indicate whether the first MAC subpdu includes a first status report.

As an embodiment, the first status report indicates an amount of uplink data (UL data volume) used to provide the MAC entity.

As a sub-embodiment of this embodiment, the uplink data amount is a sum of valid data when the first MAC PDU is first transmitted after being constructed.

As a sub-embodiment of this embodiment, the uplink data amount is a sum of valid data when the first MAC PDU is retransmitted.

As a sub-embodiment of this embodiment, the first status report is updated when the first MAC PDU is retransmitted.

As a sub-embodiment of this embodiment, the first status report is not updated when the first MAC PDU is retransmitted.

As a sub-embodiment of this embodiment, the uplink data amount does not calculate the size (size) of an RLC (Radio Link Control, radio Link layer Control protocol) header (header) and a MAC subheader (subheader).

As a sub-embodiment of this embodiment, the uplink data amount calculates the size (size) of the RLC header (header) and the MAC subheader (subheader).

As a sub-embodiment of this embodiment, the uplink data amount is a data amount on a logical channel indicated by an LCID field in the first MAC subheader.

As a sub-embodiment of this embodiment, the uplink data amount is a data amount on a logical channel group to which a logical channel indicated by the LCID field in the first MAC sub-header belongs.

As one embodiment, the first status report is used for an SDT procedure.

As one embodiment, the first status report includes a BSR.

As one embodiment, the first status report includes Inactive BSR.

As one embodiment, the first status report comprises an IBSR (Inactive BSR).

As one embodiment, the first status report includes an IDT BSR.

As one embodiment, the first status report includes an SDT BSR.

For one embodiment, the first status Report includes a DVR (Data Volume Report).

For one embodiment, the first status Report includes a DSR (Data Buffer Report).

As one embodiment, the first status Report includes a PHR (Power head room Report).

For one embodiment, the first status Report includes a BFR (Beam Failure Report).

As an embodiment, the first status report includes a Listen Before Talk failure (LBT failure).

As an embodiment, the first status report comprises Release Assistance Information (RAI) used to indicate whether there are more expected uplink or downlink transmissions by the first node.

For one embodiment, the first domain comprises an F domain.

For one embodiment, the first domain comprises an R domain.

For one embodiment, the first domain includes an F domain and an R domain.

For one embodiment, the first domain comprises a RAI domain.

As an embodiment, the size of the first field is 1 bit.

As an embodiment, the size of the first field is 2 bits.

As an embodiment, the size of the first field is 3 bits.

As an embodiment, the first domain is set to one of a first target value or a second target value.

As a sub-embodiment of this embodiment, the length of the first field is equal to 1 bit.

As a sub-embodiment of this embodiment, the length of the first field is equal to 2 bits.

As a sub-embodiment of this embodiment, the first target value and the second target value are not equal.

As a sub-embodiment of this embodiment, the first target value is equal to 1 and the second target value is equal to 0.

As a sub-embodiment of this embodiment, the first target value is equal to 0 and the second target value is equal to 1.

As a sub-embodiment of this embodiment, the first target value is equal to one of the values 00,01,10,11 and the second target value is equal to the other of the values 11,10, 00.

As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to the first target value indicating that a first status report is included in the first MAC sub-PDU; the first field in the first MAC subheader being set to the second target value indicates that a first status report is not included in the first MAC subPDU.

As a sub-embodiment of this embodiment, the first field in the first MAC subheader being set to the first target value indicates that the second field is included in the first MAC subpdu and a first status report is included in the first MAC subheader; the first domain in the first MAC sub-PDU being set to the second target value indicates that one L domain is included in the first MAC sub-PDU and that a first status report is not included in the first MAC sub-PDU; wherein the length of the one L field is equal to 1 byte.

As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a value of 00,01,10,11 other than the first target value and the second target value, reserved and not used to indicate any information.

As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to the first target value indicating the presence of the target field in this application; the first field in the first MAC subheader being set to the second target value indicates that the target field in this application does not exist.

As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to the first target value indicating that the first status report field in this application exists; the first field in the first MAC subheader being set to the second target value indicates that the first status reporting field in this application does not exist.

As a sub-embodiment of this embodiment, the setting of the first field in the first MAC subheader to the first target value indicates the presence of the second MAC payload field in this application; the first field in the first MAC subheader being set to the second target value indicates that the second MAC payload field in this application is not present.

As an embodiment, the first domain is set to one of the first given value, the second given value, the third given value, or the fourth given value.

As a sub-embodiment of this embodiment, said first given value is equal to 00, said second given value is equal to 01, said first given value is equal to 10, and said second given value is equal to 11.

As a sub-embodiment of this embodiment, the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report and release assistance information.

As a sub-embodiment of this embodiment, the setting of the first field in the first MAC subheader to a given value indicates that a first status report is included in the first MAC subpdu; wherein the one given value is one of the first given value, the second given value, the third given value, or the fourth given value.

As a sub-embodiment of this embodiment, the setting of the first field in the first MAC sub-header to a given value indicates that no first status report is included in the first MAC sub-PDU, the given value being one of the first, second, third, or fourth given values.

As a sub-embodiment of this embodiment, said first field in said first MAC subheader is set to a given value indicating that no assistance information is released; wherein the one given value is one of the first, second, third or fourth given values.

As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value indicating release assistance information; wherein the release assistance information indicates that there is no subsequent (subsequent) downlink and uplink data transmission expected (expected), the one given value being one of the first, second, third or fourth given values.

As a sub-embodiment of this embodiment, setting said first field in said first MAC subheader to a given value indicates release assistance information; wherein the release assistance information indicates that one subsequent downlink transmission is expected, the one given value being one of the first, second, third or fourth given values.

As a sub-embodiment of this embodiment, the setting of the first field in the first MAC subheader to a given value indicates that the first status report is included in the first MAC subpdu and that no auxiliary information is released; wherein the one given value is one of the first given value, the second given value, the third given value, or the fourth given value.

As a sub-embodiment of this embodiment, the setting of the first field in the first MAC subheader to a given value indicates that no first status report is included in the first MAC subpdu and that there is release assistance information; wherein the release assistance information indicates that there is no subsequent (subsequent) downlink and uplink data transmission expected (expected), the one given value being one of the first, second, third or fourth given values.

As a sub-embodiment of this embodiment, the setting of the first field in the first MAC subheader to a given value indicates that no first status report is included in the first MAC subpdu and that there is release assistance information; wherein the release assistance information indicates that one subsequent downlink transmission is expected, the one given value being one of the first, second, third or fourth given values.

As a sub-embodiment of this embodiment, the setting of the first field in the first MAC sub-header to a given value indicates that no first status report is included in the first MAC sub-PDU and no release assistance information is present; wherein the one given value is one of the first given value, the second given value, the third given value, or the fourth given value.

As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value reserved and not used to indicate any information.

As a sub-embodiment of this embodiment, any two of the first, second, third, and fourth given values are not equal.

For one embodiment, the first MAC payload includes one MAC CE.

As a sub-embodiment of this embodiment, the one MAC CE is a bit string (a bit string that is byte aligned in length) byte aligned (e.g., 8 bits) in length.

As an embodiment, the first MAC payload includes one MAC SDU.

As a sub-embodiment of this embodiment, the one MAC SDU is a bit string (a bit string of which is a bit aligned in length) byte aligned (e.g., 8 bits) in length.

As a sub-embodiment of this embodiment, the one MAC SDU is included in one MAC PDU from the first bit acknowledged.

For one embodiment, the first MAC payload includes 0 bits.

As one embodiment, the first MAC payload includes at least 1 bit.

For one embodiment, the first MAC payload includes at least 1 byte.

For one embodiment, the phrase the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload includes: the LCID field of the first MAC sub-PDU is set to a code point/index of an LCID corresponding to the first MAC payload.

As one embodiment, the phrase that the LCID field of the first MAC sub-PDU is used to indicate that a first MAC payload comprises: the LCID field of the first MAC sub-PDU indicates that the first MAC payload is included in the first MAC sub-PDU.

As one embodiment, the phrase that the LCID field of the first MAC sub-PDU is used to indicate that a first MAC payload comprises: the first MAC payload in the first MAC sub-PDU is indicated by the LCID field in the first MAC sub-PDU.

As one embodiment, the phrase that the LCID field of the first MAC sub-PDU is used to indicate that a first MAC payload comprises: the LCID field of the first MAC sub-PDU is used to indicate that the first MAC payload field of the present application is included in the first MAC sub-PDU, which includes the first MAC payload.

For one embodiment, the phrase the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload includes: the LCID field of the first MAC sub-PDU is associated with the first MAC payload.

As an embodiment, the first MAC payload is included in the first MAC sub-PDU.

As an embodiment, the first MAC subheader is placed directly before the first MAC payload.

As an embodiment, the first MAC subheader is placed directly before the second MAC payload.

For one embodiment, the first MAC load is associated with an LCID.

For one embodiment, the first MAC payload corresponds to an LCID.

For one embodiment, the first MAC payload includes a CCCH SDU.

As an embodiment, the first MAC payload includes a DTCH SDU.

As an embodiment, the first MAC payload comprises a DCCH SDU.

As an embodiment, the first MAC payload includes a MAC SDU.

For one embodiment, the first MAC payload includes a MAC CE.

As one embodiment, the phrase that the first domain is one of the first MAC subheader except for the LCID domain includes: the first domain belongs to the first MAC subheader and the first domain is not the LCID domain.

As one embodiment, the phrase that the first domain is one of the first MAC subheader except for the LCID domain includes: the first domain is the R domain of section 6.1.2 in 3gpp TS 38.321.

As one embodiment, the phrase that the first domain is one of the first MAC subheader except for the LCID domain includes: the first domain is the F domain of section 6.1.2 in 3gpp TS 38.321.

As one embodiment, the phrase that the first domain is one of the first MAC subheader except for the LCID domain includes: the first domain is the L domain of section 6.1.2 in 3gpp TS 38.321.

As one embodiment, the phrase that the first domain is one of the first MAC subheader except for the LCID domain includes: the first domain is all of the L domain of section 6.1.2 in 3gpp TS 38.321.

As one embodiment, the phrase that the first domain is one of the first MAC subheader except for the LCID domain includes: the first domain is part of the L domain of section 6.1.2 in 3gpp TS 38.321.

As one embodiment, the phrase that the first domain is one of the first MAC subheader except for the LCID domain includes: the first domain is an R domain of section 6.1.2 in 3gpp TS38.321, or at least one of an F domain or an L domain.

As one embodiment, the phrase that the first field is a field of the first MAC subheader other than the LCID field includes: the first domain is at least one of an R domain of section 6.1.2 in 3gpp TS38.321, or an F domain.

As one embodiment, the phrase that the first domain is one of the first MAC subheader except for the LCID domain includes: the first domain is at least one of an R domain of section 6.1.2 in 3gpp TS38.321, or an F domain.

As one embodiment, the phrase that the first domain is one of the first MAC subheader except for the LCID domain includes: the first domain is an R domain of section 6.1.2 in 3gpp TS38.321, or at least one of all or part of an F domain or an L domain.

As one embodiment, the phrase that the first domain is one of the first MAC subheader except for the LCID domain includes: the first domain is at least one of an R domain, or an F domain, or an L domain, or an LCID domain of section 6.1.2 in 3gpp TS 38.321.

As one embodiment, the phrase that the first domain is one of the first MAC subheader except for the LCID domain includes: the first domain is at least one of an R domain, or an F domain, or all or part of an L domain, or all or part of an LCID domain of section 6.1.2 in 3gpp TS 38.321.

As an embodiment, the LCID field indicates a logical channel instance (local channel instance of the correlating MAC SDU) of the corresponding MAC SDU or a type (the type of the correlating MAC CE) or padding of the corresponding MAC CE.

As an embodiment, the LCID field includes 6 bits, where the 6 bits are used to determine 64 code points (codepoints)/indexes (indexes), and one of the 64 code points/indexes indicates a logical channel instance of a corresponding MAC SDU or a type or padding of a corresponding MAC CE.

As one embodiment, the phrase that the first MAC payload is not the first status report includes: the first status report does not belong to the first MAC payload.

As one embodiment, the phrase that the first MAC payload is not the first status report includes: the first MAC carries a first MAC SDU, and the first status report is not a MAC SDU.

As one embodiment, the phrase that the first MAC payload is not the first status report includes: the first MAC payload is one MAC CE and the first status report is not the one MAC CE.

As one embodiment, the phrase that the first MAC payload is not the first status report includes: the first MAC load and the first status report carry different information.

As one embodiment, the phrase that the first MAC payload is not the first status report includes: the first status report is not included in the first MAC payload.

As an embodiment, the first status report is used for Beam Failure Recovery (BFR) reporting.

As a sub-embodiment of this embodiment, the LCID field is not set to 50 or 51.

As a sub-embodiment of this embodiment, when the LCID field is set to 34, the eLCID field is not set to 251.

As an embodiment, the first status report is used for data volume reporting.

As a sub-embodiment of this embodiment, the LCID field is not set to 59, or 60, or 61, or 62.

As a sub-embodiment of this embodiment, the LCID field is not set to 45 or 46.

As a sub-embodiment of this embodiment, when the LCID field is set to 34, the eLCID field is not set to 255.

For one embodiment, the first status report is used for Power Headroom Reporting (PHR).

As a sub-embodiment of this embodiment, the LCID field is not set to 54, or 56, or 57.

As a sub-embodiment of this embodiment, the LCID field is not set to 45 or 46.

As a sub-embodiment of this embodiment, when the LCID field is set to 34, the elicid field is not set to 255.

As an embodiment, the first status report is used for listen-before-talk failure reporting.

As a sub-embodiment of this embodiment, the LCID field is not set to 45 or 46.

As an embodiment, the first status report is used to release assistance information.

As a sub-embodiment of this embodiment, the LCID field is set to an integer no less than 0 and no greater than 63.

As a sub-embodiment of this embodiment, the LCID field is equal to 33, the eLCID field is set to not less than 0 and not more than 2 ¹⁶ -an integer of 1.

As a sub-embodiment of this embodiment, the LCID field is equal to 34, and the eLCID field is set to an integer not less than 0 and not more than 249.

As an embodiment, the definition of the etlcid domain in the present application refers to section 6.2.1 in 3gpp ts38.321.

As an embodiment, the L domain in this application refers to the L domain in section 6.2.1 of 3gpp ts 38.321.

As an embodiment, the F domain in this application refers to an F domain in section 6.2.1 of 3gpp ts38.321.

As an embodiment, the length of the R field in this application is equal to 1 bit or 2 bits.

As an embodiment, the R field in the present application is set to 0.

As an embodiment, the first domain in this application includes at least one of the F domain or the R domain.

As an embodiment, the first domain in this application does not include the F domain or the R domain.

As an embodiment, the first domain in this application is not the F domain or the R domain.

As an embodiment, the first field in this application reuses the position of the F field or the R field in the MAC subheader.

As an embodiment, the first field in this application is a field in a MAC subheader that is redefined.

As an embodiment, the target domain in the present application includes the L domain.

As an embodiment, the target domain in the present application does not include the L domain.

As an embodiment, the target domain in the present application is not the L domain.

As an embodiment, the target field in the present application is a field in a MAC subheader redefined.

As an embodiment, the second MAC payload field and the first MAC payload field in the present application use the first MAC subheader together.

Example 2

Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in fig. 2. Fig. 2 illustrates a diagram of a network architecture 200 of a 5G NR (New Radio, new air interface), LTE (Long-Term Evolution ), and LTE-a (Long-Term Evolution Advanced) system. The 5G NR or LTE network architecture 200 may be referred to as a 5GS (5G System)/EPS (Evolved Packet System) 200 or some other suitable terminology. The 5GS/EPS 200 may include one or more UEs (User Equipment) 201, ng-RANs (next generation radio access networks) 202,5gc (5G Core networks )/EPC (Evolved Packet Core) 210, hss (Home Subscriber Server)/UDM (Unified Data Management) 220, and internet services 230. The 5GS/EPS may interconnect with other access networks, but these entities/interfaces are not shown for simplicity. As shown, the 5GS/EPS provides packet switched services, however those skilled in the art will readily appreciate that the various concepts presented throughout this application may be extended to networks providing circuit switched services or other cellular networks. The NG-RAN includes NR node bs (gnbs) 203 and other gnbs 204. The gNB203 provides user and control plane protocol termination towards the UE 201. The gnbs 203 may be connected to other gnbs 204 via an Xn interface (e.g., backhaul). The gNB203 may also be referred to as a base station, a base transceiver station, a radio base station, a radio transceiver, a transceiver function, a Basic Service Set (BSS), an Extended Service Set (ESS), a TRP (transmitting receiving node), or some other suitable terminology. The gNB203 provides the UE201 with an access point to the 5GC/EPC210. Examples of the UE201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop, a Personal Digital Assistant (PDA), a satellite radio, non-terrestrial base station communications, satellite mobile communications, a global positioning system, a multimedia device, a video device, a digital audio player (e.g., MP3 player), a camera, a game console, a drone, an aircraft, a narrowband internet of things device, a machine type communication device, a terrestrial vehicle, an automobile, a wearable device, or any other similar functioning device. Those skilled in the art may also refer to UE201 as a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile client, a client, or some other suitable terminology. The gNB203 is connected to the 5GC/EPC210 via an S1/NG interface. The 5GC/EPC210 includes MME (Mobility Management Entity)/AMF (Authentication Management Field)/SMF (Session Management Function) 211, other MME/AMF/SMF214, S-GW (serving Gateway)/UPF (User Plane Function) 212, and P-GW (Packet data Network Gateway)/UPF 213.MME/AMF/SMF211 is a control node that handles signaling between UE201 and 5GC/EPC210. In general, the MME/AMF/SMF211 provides bearer and connection management. All user IP (Internet protocol) packets are transported through the S-GW/UPF212, which S-GW/UPF212 itself is connected to the P-GW/UPF213. The P-GW provides UE IP address allocation as well as other functions. The P-GW/UPF213 is connected to the internet service 230. The internet service 230 includes an operator-corresponding internet protocol service, and may specifically include the internet, an intranet, an IMS (IP Multimedia Subsystem), and a packet-switched streaming service.

As an embodiment, the UE201 corresponds to the first node in this application.

As an embodiment, the UE201 is a User Equipment (UE).

As an embodiment, the gNB203 corresponds to the second node in this application.

As an embodiment, the gNB203 is a base station equipment (BS).

As an embodiment, the gNB203 is a user equipment.

As an embodiment, the gNB203 is a relay.

As an embodiment, the gNB203 is a Gateway (Gateway).

As an embodiment, the user equipment supports transmission of a Non-Terrestrial Network (NTN).

As an embodiment, the user equipment supports transmission of a non-Terrestrial Network (Terrestrial Network).

As an embodiment, the user equipment supports transmission in a large delay-difference network.

As an embodiment, the user equipment supports Dual Connection (DC) transmission.

As one embodiment, the user device comprises an aircraft.

As an embodiment, the user equipment comprises a vehicle-mounted terminal.

As one embodiment, the user equipment comprises a watercraft.

As an embodiment, the user equipment includes an internet of things terminal.

As an embodiment, the user equipment comprises a terminal of an industrial internet of things.

For one embodiment, the user equipment comprises a device supporting low-latency high-reliability transmission.

As an embodiment, the user equipment comprises a test equipment.

As an embodiment, the user equipment comprises a signaling tester.

As one embodiment, the base station apparatus supports transmission in a non-terrestrial network.

As an embodiment, the base station apparatus supports transmission in a large delay-difference network.

As an embodiment, the base station apparatus supports transmission of a terrestrial network.

As an embodiment, the base station device includes a macro Cellular (Marco Cellular) base station.

As one embodiment, the base station apparatus includes a Micro Cell base station.

As one embodiment, the base station apparatus includes a Pico Cell (Pico Cell) base station.

As one embodiment, the base station apparatus includes a home base station (Femtocell).

As an embodiment, the base station apparatus includes a base station apparatus supporting a large delay difference.

As one embodiment, the base station device includes a flying platform device.

For one embodiment, the base station device comprises a satellite device.

As an embodiment, the base station device includes a TRP (Transmitter Receiver Point).

As an embodiment, the base station apparatus includes a CU (Centralized Unit).

As an embodiment, the base station apparatus includes a DU (Distributed Unit).

As an embodiment, the base station device comprises a test device.

As one embodiment, the base station apparatus includes a signaling tester.

As an embodiment, the base station device includes an IAB (Integrated Access and Backhaul) -node.

For one embodiment, the base station equipment includes an IAB-donor.

For one embodiment, the base station equipment comprises an IAB-donor-CU.

As an embodiment, the base station equipment comprises an IAB-donor-DU.

As an embodiment, the base station device comprises an IAB-DU.

For one embodiment, the base station device includes an IAB-MT.

As one embodiment, the relay includes a relay.

As one embodiment, the relay includes an L3 relay.

As one embodiment, the relay includes an L2 relay.

For one embodiment, the relay comprises a router.

As one embodiment, the relay includes a switch.

As one embodiment, the relay includes a user equipment.

As one embodiment, the relay includes a base station apparatus.

Example 3

Embodiment 3 shows a schematic diagram of an embodiment of a radio protocol architecture for a user plane and a control plane according to the present application, as shown in fig. 3. Fig. 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for the user plane 350 and the control plane 300, fig. 3 showing the radio protocol architecture for the control plane 300 with three layers: layer 1, layer 2 and layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY301. A layer 2 (L2 layer) 305 is above the PHY301, and includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control Protocol) sublayer 303, and a PDCP (Packet Data Convergence Protocol) sublayer 304. The PDCP sublayer 304 provides multiplexing between different radio bearers and logical channels. The PDCP sublayer 304 also provides security by ciphering packets and provides handover support. The RLC sublayer 303 provides segmentation and reassembly of upper layer packets, retransmission of lost packets, and reordering of packets to compensate for out-of-order reception due to HARQ. The MAC sublayer 302 provides multiplexing between logical and transport channels. The MAC sublayer 302 is also responsible for allocating various radio resources (e.g., resource blocks) in one cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in layer 3 (L3 layer) in the Control plane 300 is responsible for obtaining Radio resources (i.e., radio bearers) and configuring the lower layers using RRC signaling. The radio protocol architecture of the user plane 350, which includes layer 1 (L1 layer) and layer 2 (L2 layer), is substantially the same in the user plane 350 for the physical layer 351, the PDCP sublayer 354 in the L2 layer 355, the RLC sublayer 353 in the L2 layer 355, and the MAC sublayer 352 in the L2 layer 355 as the corresponding layers and sublayers in the control plane 300, but the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 further includes an SDAP (Service Data Adaptation Protocol) sublayer 356, and the SDAP sublayer 356 is responsible for mapping between QoS streams and Data Radio Bearers (DRBs) to support diversity of services.

As an example, the wireless protocol architecture in fig. 3 is applicable to the first node in this application.

The radio protocol architecture of fig. 3 applies to the second node in this application as an example.

As an embodiment, the first message in this application is generated in the RRC306.

As an embodiment, the first message in this application is generated in the MAC302 or the MAC352.

As an embodiment, the first message in the present application is generated in the PHY301 or the PHY351.

As an embodiment, the first signaling in this application is generated in the RRC306.

As an embodiment, the first signaling in this application is generated in the MAC302 or the MAC352.

As an embodiment, the first signaling in the present application is generated in the PHY301 or the PHY351.

As an embodiment, the first MAC PDU in this application is generated in the RRC306.

As an embodiment, the first MAC PDU in the present application is generated in the PDCP 304 or PDCP 354.

As an embodiment, the first MAC PDU in the present application is generated in the RLC 303 or the RLC 353.

As an embodiment, the first MAC PDU in the present application is generated in the MAC302 or the MAC352.

Example 4

Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in fig. 4. Fig. 4 is a block diagram of a first communication device 450 and a second communication device 410 communicating with each other in an access network.

The first communications device 450 includes a controller/processor 459, a memory 460, a data source 467, a transmit processor 468, a receive processor 456, a multi-antenna transmit processor 457, a multi-antenna receive processor 458, a transmitter/receiver 454, and an antenna 452.

The second communications device 410 includes a controller/processor 475, a memory 476, a receive processor 470, a transmit processor 416, a multiple antenna receive processor 472, a multiple antenna transmit processor 471, a transmitter/receiver 418 and an antenna 420.

In the transmission from the second communication device 410 to the first communication device 450, at the second communication device 410, upper layer data packets from the core network are provided to the controller/processor 475. The controller/processor 475 implements the functionality of the L2 layer. In transmissions from the second communications device 410 to the first communications device 450, the controller/processor 475 provides header compression, encryption, packet segmentation and reordering, multiplexing between logical and transport channels, and radio resource allocation to the first communications device 450 based on various priority metrics. The controller/processor 475 is also responsible for retransmission of lost packets and signaling to the first communication device 450. The transmit processor 416 and the multi-antenna transmit processor 471 implement various signal processing functions for the L1 layer (i.e., the physical layer). The transmit processor 416 implements coding and interleaving to facilitate Forward Error Correction (FEC) at the second communication device 410, as well as mapping of signal constellation based on various modulation schemes (e.g., binary Phase Shift Keying (BPSK), quadrature Phase Shift Keying (QPSK), M-phase shift keying (M-PSK), M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based precoding and non-codebook based precoding, and beamforming on the coded and modulated symbols to generate one or more spatial streams. Transmit processor 416 then maps each spatial stream to subcarriers, multiplexes with reference signals (e.g., pilots) in the time and/or frequency domain, and then uses an Inverse Fast Fourier Transform (IFFT) to generate the physical channels carrying the time-domain multicarrier symbol streams. The multi-antenna transmit processor 471 then performs analog precoding/beamforming operations on the time domain multi-carrier symbol stream. Each transmitter 418 converts the baseband multi-carrier symbol stream provided by the multi-antenna transmit processor 471 into a radio frequency stream that is then provided to a different antenna 420.

In a transmission from the second communications apparatus 410 to the first communications apparatus 450, each receiver 454 receives a signal through its respective antenna 452 at the first communications apparatus 450. Each receiver 454 recovers information modulated onto a radio frequency carrier and converts the radio frequency stream into a baseband multi-carrier symbol stream that is provided to a receive processor 456. Receive processor 456 and multi-antenna receive processor 458 implement the various signal processing functions of the L1 layer. A multi-antenna receive processor 458 performs receive analog precoding/beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. Receive processor 456 converts the baseband multicarrier symbol stream after the receive analog precoding/beamforming operation from the time domain to the frequency domain using a Fast Fourier Transform (FFT). In the frequency domain, the physical layer data signals and the reference signals to be used for channel estimation are demultiplexed by the receive processor 456, and the data signals are subjected to multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered at a receive processor 456 and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communications device 410 on the physical channel. The upper layer data and control signals are then provided to a controller/processor 459. The controller/processor 459 implements the functions of the L2 layer. The controller/processor 459 may be associated with a memory 460 that stores program codes and data. Memory 460 may be referred to as a computer-readable medium. In transmissions from the second communications device 410 to the second communications device 450, the controller/processor 459 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the core network. The upper layer packet is then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.

In a transmission from the first communications device 450 to the second communications device 410, a data source 467 is used at the first communications device 450 to provide upper layer data packets to a controller/processor 459. Data source 467 represents all protocol layers above the L2 layer. Similar to the send function at the second communications apparatus 410 described in the transmission from the second communications apparatus 410 to the first communications apparatus 450, the controller/processor 459 implements header compression, encryption, packet segmentation and reordering, and multiplexing between logical and transport channels based on radio resource allocation, implementing L2 layer functions for the user plane and control plane. The controller/processor 459 is also responsible for retransmission of lost packets and signaling to said second communications device 410. A transmit processor 468 performs modulation mapping, channel coding, and digital multi-antenna spatial precoding by a multi-antenna transmit processor 457 including codebook-based precoding and non-codebook based precoding, and beamforming, and the transmit processor 468 then modulates the resulting spatial streams into multi-carrier/single-carrier symbol streams, which are provided to different antennas 452 via a transmitter 454 after analog precoding/beamforming in the multi-antenna transmit processor 457. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a radio frequency symbol stream and provides the radio frequency symbol stream to the antenna 452.

In a transmission from the first communication device 450 to the second communication device 410, the functionality at the second communication device 410 is similar to the receiving functionality at the first communication device 450 described in the transmission from the second communication device 410 to the first communication device 450. Each receiver 418 receives an rf signal through its respective antenna 420, converts the received rf signal to a baseband signal, and provides the baseband signal to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multiple antenna receive processor 472 collectively implement the functions of the L1 layer. The controller/processor 475 implements the L2 layer functions. The controller/processor 475 can be associated with a memory 476 that stores program codes and data. Memory 476 may be referred to as a computer-readable medium. In transmission from the first communications device 450 to the second communications device 410, the controller/processor 475 provides demultiplexing between transport and logical channels, packet reassembly, deciphering, header decompression, control signal processing to recover upper layer packets from the UE 450. Upper layer data packets from the controller/processor 475 may be provided to a core network.

As an embodiment, the first communication device 450 includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code configured to, for use with the at least one processor, the first communication device 450 at least: establishing a first MAC PDU; transmitting the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload; wherein the first domain is one of the first MAC subheader except for the LCID domain; the first MAC payload is not the first status report.

As an embodiment, the first communication device 450 includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: building a first MAC PDU; transmitting the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload; wherein the first domain is one of the first MAC subheader other than the LCID domain; the first MAC payload is not the first status report.

As an embodiment, the second communication device 410 includes: at least one processor and at least one memory including computer program code; the at least one memory and the computer program code are configured for use with the at least one processor. The second communication device 410 at least: receiving a first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload; wherein the first MAC PDU is constructed; the first domain is one of the first MAC subheader except the LCID domain; the first MAC payload is not the first status report.

As an embodiment, the second communication device 410 includes: a memory storing a program of computer readable instructions that when executed by at least one processor result in actions comprising: receiving a first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload; wherein the first MAC PDU is assembled; the first domain is one of the first MAC subheader except the LCID domain; the first MAC payload is not the first status report.

For one embodiment, the antenna 452, the receiver 454, the receive processor 456, the controller/processor 459 are configured to receive a first signaling; at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller/processor 475 is configured to send first signaling.

As one implementation, the antenna 452, the transmitter 454, the transmit processor 468, the controller/processor 459 are used to send a first MAC PDU; at least one of the antenna 420, the receiver 418, the receive processor 470, the controller/processor 475 is configured to receive a first MAC PDU.

As one implementation, the antenna 452, the transmitter 454, the transmit processor 468, the controller/processor 459 are configured to send a first message; at least one of the antenna 420, the receiver 418, the receive processor 470, the controller/processor 475 is configured to receive a first message.

As an embodiment, the first communication device 450 corresponds to a first node in the present application.

As an embodiment, the second communication device 410 corresponds to a second node in the present application.

For one embodiment, the first communication device 450 is a user device.

As an embodiment, the first communication device 450 is a user equipment supporting a large delay difference.

As an embodiment, the first communication device 450 is a user equipment supporting NTN.

As an example, the first communication device 450 is an aircraft device.

For one embodiment, the first communication device 450 is location-enabled.

As an example, the first communication device 450 does not have the capability to subscribe.

As an embodiment, the first communication device 450 is a TN-enabled user equipment.

As an embodiment, the first communication device 450 is an internet of things terminal.

As an example, the first communication device 450 is a V2X terminal.

As an embodiment, the second communication device 410 is a base station device (gNB/eNB/ng-eNB).

As an embodiment, the second communication device 410 is a base station device supporting large delay inequality.

As an embodiment, the second communication device 410 is a base station device supporting NTN.

For one embodiment, the second communication device 410 is a satellite device.

For one embodiment, the second communication device 410 is a flying platform device.

As an embodiment, the second communication device 410 is a base station device supporting TN.

For one embodiment, the second communication device 410 is a user device.

Example 5

Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in fig. 5. It is specifically noted that the order in this example does not limit the order of signal transmission and the order of implementation in this application.

For theFirst node U01In step S5101, a first signaling is received; in step S5102, a first MAC PDU is established; in step S5103, the first MAC PDU is transmitted.

ForSecond node N02In step S5201, the first signaling is transmitted; in step S5202, the first MAC PDU is received.

In embodiment 5, the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload; the first domain is one of the first MAC subheader except the LCID domain; the first MAC payload is not the first status report; the first signaling is used to determine whether the first domain is used to indicate whether the first MAC sub-PDU includes a first status report.

As one embodiment, the phrase the first signaling is used to determine whether the first field is used to indicate whether the first MAC sub-PDU includes a first status report includes: the first signaling indicates whether the first domain is used to indicate whether the first MAC sub-PDU includes a first status report.

As one embodiment, the phrase the first signaling is used to determine whether the first field is used to indicate whether the first MAC sub-PDU includes a first status report includes: the first signaling is used to determine that the first field is used to indicate that the first MAC sub-PDU includes a first status report.

As one embodiment, the phrase the first signaling is used to determine whether the first field is used to indicate whether the first MAC sub-PDU includes a first status report includes: the first signaling is used to determine that the first domain is not used to indicate whether the first MAC sub-PDU includes a first status report.

As an embodiment, the first signaling is transmitted over an air interface.

As an embodiment, the first signaling is sent through an antenna port.

As an embodiment, the first signaling includes an Uplink (UL) signal.

As an embodiment, the first signaling includes a Sidelink (SL) signal.

As an embodiment, the first signaling comprises an RRC message.

As an embodiment, the first signaling includes an rrcreelease message or an RRCConnectionRelease.

As an embodiment, the first signaling includes at least one IE (Information Element) in an RRC message.

As an embodiment, the first signaling comprises a field in an RRC message.

As a sub-embodiment of this embodiment, the one RRC message includes RRCRelease or RRCConnectionRelease.

As a sub-embodiment of this embodiment, the one RRC message includes SIB1 (System Information Block 1).

As a sub-embodiment of this embodiment, the one RRC message includes rrcreeconfiguration or RRCConnectionReconfiguration.

As a sub-embodiment of this embodiment, the one field set to setup indicates that the first field is used to indicate whether the first MAC sub-PDU includes a first status report.

As a sub-embodiment of this embodiment, the one field is set to release to indicate that the first field is not used to indicate whether the first MAC sub-PDU includes a first status report.

As a sub-embodiment of this embodiment, the one field is set to release indicating that the first field is used to indicate the length of the first MAC payload field.

As a sub-embodiment of this embodiment, the one field set to tune indicates that the first field is used to indicate whether the first MAC sub-PDU includes a first status report.

As a sub-embodiment of this embodiment, the one field is not set to indicate that the first field is not used to indicate whether the first MAC sub-PDU includes the first status report.

As a sub-embodiment of this embodiment, the one domain is not set indicating that the first domain is used to indicate the length of the first MAC payload domain.

As an embodiment, when the first domain is set to a first target value, the first MAC subheader includes the first status report; or when the first domain is set to a second target value, the first MAC subheader does not include the first status report.

As one embodiment, the first MAC subheader includes the first status report when the first domain is set to a first target value.

As one embodiment, the first MAC subheader does not include the first status report when the first domain is set to a second target value.

As an embodiment, the first status report belongs to the first MAC subheader.

As an embodiment, the phrase that the first status report belongs to the first MAC subheader includes: one field in the first MAC subheader indicates the first status report.

As an embodiment, the phrase that the first status report belongs to the first MAC subheader includes: the first MAC subheader includes the first status report.

As an embodiment, the phrase that the first status report belongs to the first MAC subheader includes: the first status report is determined by the first MAC subheader.

As an embodiment, the phrase that the first status report belongs to the first MAC subheader includes: a field used to indicate the first status report belongs to the first MAC subheader.

As an embodiment, the phrase that the first status report belongs to the first MAC subheader includes: the first MAC subheader includes a target field including the first status report.

As a sub-embodiment of this embodiment, the sentence "the first MAC subheader includes a target field including the first status report" includes: the first MAC subheader comprises a target domain, the target domain comprises a first status report domain, and the first status report domain comprises the first status report.

As one embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report includes: the first field in the first MAC subheader indicates whether the first MAC subpdu includes the target field of the present application, which includes a first status report.

As a sub-embodiment of this embodiment, the target field comprises a first status reporting field comprising the first status report.

As a sub-embodiment of this embodiment, the target domain consists of a first status reporting domain, which includes the first status report.

As a sub-embodiment of this embodiment, the target domain is composed of a first status reporting domain and other domains, and the first status reporting domain includes the first status report.

As a sub-embodiment of this embodiment, the name of the target domain is Buffer Size.

As a sub-embodiment of this embodiment, the name of the target domain is the Data Volume.

As a sub-embodiment of this embodiment, the name of the target domain is Data Size.

As a sub-embodiment of this embodiment, the name of the target domain is Inactive Buffer Size.

As a sub-embodiment of this embodiment, the name of the target domain is SDT Buffer Size.

As a sub-embodiment of this embodiment, the name of the target domain is IDT Buffer Size.

As a sub-embodiment of this embodiment, the target field is an L field in the first MAC subheader.

As a sub-embodiment of this embodiment, the target field is a buffer size field in the first MAC subheader.

As a sub-embodiment of this embodiment, the destination field is a data volume field in the first MAC subheader.

As a sub-embodiment of this embodiment, the length of the target field is equal to 8 bits.

As a sub-embodiment of this embodiment, the length of the target field is equal to 9 bits.

As a sub-embodiment of this embodiment, the length of the target field is equal to 10 bits.

As a sub-embodiment of this embodiment, the length of the target field is equal to 16 bits.

As an embodiment, the first MAC sub-PDU comprises a second MAC payload comprising the first status report.

As an embodiment, the second MAC payload does not belong to the first MAC subheader.

For one embodiment, the second MAC load is different from the first MAC load.

As one embodiment, the LCID field of the first MAC sub-PDU does not uniquely indicate the second MAC payload.

As an embodiment, the second MAC payload is a MAC CE or a MAC SDU or padding (padding).

As one embodiment, the second MAC payload is not assigned a dedicated LCID.

As an embodiment, the second MAC payload has no dedicated MAC subheader.

As an embodiment, the second MAC payload field is placed directly before the first MAC payload field.

As an embodiment, the first MAC payload field is placed directly before the second MAC payload field.

As an embodiment, when the first domain is set to a first target value, the first MAC sub-PDU includes a second MAC payload; or, the first MAC sub-PDU does not include the second MAC payload when the first domain is set to the second target value.

As one embodiment, the first MAC sub-PDU includes a second MAC payload when the first domain is set to a first target value.

As an embodiment, the first MAC sub-PDU does not include the second MAC payload when the first domain is set to the second target value.

As one embodiment, the phrase that the first MAC sub-PDU includes the second MAC payload includes: the second MAC payload is part of the first MAC sub-DPU.

As one embodiment, the phrase that the first MAC sub-PDU includes the second MAC payload includes: the first MAC sub-PDU includes the first MAC sub-header, the first MAC payload, and the second MAC payload.

As one embodiment, the phrase that the first MAC sub-PDU includes the second MAC payload includes: the first MAC sub-PDU includes a second MAC payload domain that includes the second MAC payload.

As an embodiment, the phrase that the second MAC payload includes the first status report includes: the second MAC payload includes at least the first status report.

As one embodiment, the phrase that the second MAC payload includes the first status report includes: the first status report belongs to the second MAC load.

As an embodiment, the phrase that the second MAC payload includes the first status report includes: the second MAC load is the first status report.

As one embodiment, the phrase that the second MAC payload includes the first status report includes: the first status report is part of the second MAC payload.

As an embodiment, the sentence "the first MAC sub-PDU includes a second MAC payload including the first status report" includes: the first MAC sub-PDU includes a second MAC payload domain including the second MAC payload including the first status report.

As a sub-embodiment of this embodiment, the second MAC load domain comprises a first status reporting domain, and the first status reporting domain comprises the first status report.

As a sub-embodiment of this embodiment, the second MAC payload field is composed of a first status report field, and the first status report field includes the first status report.

As a sub-embodiment of this embodiment, the second MAC load domain is composed of a first status report domain and other domains, and the first status report domain includes the first status report.

As one embodiment, the phrase that the second MAC payload includes the first status report includes: the second MAC payload is used for carrying the first status report

As one embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report includes: the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes the second MAC payload in this application, which includes the first status report.

As one embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report includes: the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes the second MAC payload field of the present application, which includes a first status report.

As one embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC subpdu includes a first status report includes: the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes the second MAC payload field of the present application, the second MAC payload field including the second MAC payload, the second MAC payload including the first status report.

As an embodiment, a second field is included in the first MAC sub-PDU, the second field indicating at least a length of the first MAC payload, the unit of the length being a byte (byte).

As a sub-embodiment of this embodiment, the length of the second field is equal to 7 bits.

As a sub-embodiment of this embodiment, the length of the second field is equal to 8 bits, and the 8 bits are equal to 1 byte.

As a sub-embodiment of this embodiment, the length of the second field is equal to 9 bits.

As a sub-embodiment of this embodiment, the length of the second field is equal to 15 bits.

As a sub-embodiment of this embodiment, the length of the second field is equal to 16 bits, and the 16 bits are equal to 2 bytes.

As a sub-embodiment of this embodiment, the length of the second field is equal to 24 bits, and the 24 bits are equal to 3 bytes.

As a sub-embodiment of this embodiment, the length of the second field is equal to 32 bits, and the 32 bits are equal to 4 bytes.

As a sub-embodiment of this embodiment, the second field occupies a byte in the first MAC subheader that immediately follows the L field.

As a sub-embodiment of this embodiment, the second field occupies the most significant bit in the first MAC subheader and a byte immediately following the L field.

As a sub-embodiment of this embodiment, the second field occupies the most significant bit in the first MAC subheader and a byte immediately following the LCID field.

As a sub-embodiment of this embodiment, the phrase the second field indicates at least a length of the first MAC payload includes: the second field indicates a length of the first MAC payload.

As a sub-embodiment of this embodiment, the phrase the second field indicates at least a length of the first MAC payload includes: the second field indicates a length of the first MAC payload and the second MAC payload.

As a sub-embodiment of this embodiment, the first MAC subheader is composed of the first field, the LCID field, and a second field.

In one embodiment, the first MAC subheader includes at least a first field, a second field, and an LCID field.

As an embodiment, the second field is not included in the first MAC sub-PDU.

As an embodiment, the dashed box F5.1 is optional.

As an example, the dashed box F5.1 exists.

As an example, the dashed box F5.1 is not present.

Example 6

Embodiment 6 illustrates a flow chart of wireless signal transmission according to another embodiment of the present application, as shown in fig. 6. It is specifically noted that the order in this example does not limit the order of signal transmission and the order of implementation in this application.

ForFirst node U01In step S6101, a first signaling is received; in step S6102, the first DRB is recovered along with the first message; in step S6103, a first message is sent; in step S6104, recovering the first DRB along with the first message; in step S6105, a first condition set is satisfied; in step S6106, in response to the first set of conditions being met, a first status report is triggered; in step S6107, a first MAC PDU is constructed; in step S6At 108, a first MAC PDU is transmitted.

For theSecond node N02In step S6201, the first signaling is sent; in step S6202, receiving the first message; in step S6203, the first MAC PDU is received.

In embodiment 6, the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload; the first domain is one of the first MAC subheader except the LCID domain; the first MAC load is not the first status report; the first message is used for a first RRC recovery procedure; the first set of conditions includes that the first RRC recovery procedure is being performed and a first data block is in effect, the first data block being associated with the first DRB; the first status report indicates a cache-related status; the first signaling is used to determine whether the first domain is used to indicate whether the first MAC sub-PDU includes a first status report.

As an embodiment, the first message is sent in an RRC INACTIVE (RRC _ INACTIVE) state.

As an embodiment, the first message is sent in an RRC IDLE (RRC IDLE) state.

For one embodiment, the first message is transmitted over an air interface.

For one embodiment, the first message is sent through an antenna port.

For one embodiment, the first message includes an Uplink (UL) signal.

As an embodiment, the first message includes a Sidelink (SL) signal.

As an embodiment, the first message is transmitted through SRB0 (signaling Radio Bearer 0).

As an embodiment, the first message is transmitted through SRB1 (signaling Radio Bearer 1).

As an embodiment, the first message is transmitted through SRB2 (signaling Radio Bearer 2).

As an embodiment, the first message is transmitted through SRB3 (signaling Radio Bearer 3).

As an embodiment, the first message is transmitted over a Common Control Channel (CCCH).

As an embodiment, the first message is transmitted over a DCCH (Common Control Channel).

As an embodiment, the first message includes an RRC (Radio Resource Control) message.

As an embodiment, the first message includes at least one IE (Information Element) in an RRC message.

As an embodiment, the first message includes at least one Field (Field) in an RRC message.

As an embodiment, the first message includes a MAC (Medium Access Control) PDU (Protocol Data Unit), where the MAC PDU includes a MAC SDU (Service Data Unit), and the MAC SDU carries the RRC message.

As a sub-embodiment of this embodiment, the one MAC SDU comprises a CCCH SDU.

As a sub-embodiment of this embodiment, the one MAC SDU comprises a DCCH SDU.

As a sub-embodiment of this embodiment, the one MAC SDU includes a DTCH (Dedicated Traffic Channel) SDU.

As an embodiment, the first message includes a rrcresemequest message or a rrcresemequest 1 message.

As an embodiment, the first message includes an RRCConnectionResumeRequest message or an RRCEarlyDataRequest message.

As an embodiment, the first message includes an RRC message with a name including at least one of RRC, connection, resume, sdt, idt, inactive, small, data, transmission, or Request.

For one embodiment, the first message comprises a rrcreconconfiguresildenk message.

As an embodiment, the first message includes an MCGFailureInformation message, or an rrcreetabilstringrequest message, or an RRCSetupRequest message.

In one embodiment, the first message includes at least one of shortI-RNTI-Value, I-RNTI-Value, resummeMAC-I, resummeCause, or spare.

As a sub-embodiment of this embodiment, the first message includes resummemac-I, which is a bit string with length equal to 16.

As a sub-embodiment of this embodiment, the first message includes resumecuse, where the resumecuse indicates one of empty or highroyyaccess, mt-Access, mo-signaling, mo-Data, mo-VoiceCall, mo-VideoCall, mo-SMS, rna-Update, ps-PriorityAccess, mc-PriorityAccess, sdt, idt, edt, smalldatatransmission, inactivatatransmission or pur.

As an embodiment, the spare is a bit string with a length equal to 1.

As an embodiment, the first Message is all or part of Message 3 (Message 3, msg3).

As an embodiment, the first Message is all or part of a Message a (Message a, msgA).

As an embodiment, the sentence "along with the first message, recovering at least a first DRB" includes: recovering at least the first DRB when the first message is ready to be sent.

As an embodiment, the sentence "along with the first message, recovering at least a first DRB" includes: when the content of the first message is set to be completed, recovering at least the first DRB.

As an embodiment, the sentence "along with the first message, recovering at least a first DRB" includes: recovering at least the first DRB after the first message is sent.

As an embodiment, the sentence "along with the first message, recovering at least a first DRB" includes: when the content of the first message is set to completion and before delivery to a lower layer, recovering at least the first DRB.

As an embodiment, the first DRB comprises at least one DRB.

As an embodiment, the first DRB is used for SDT.

As one embodiment, the first DRB is used for IDT (Inactive Data Transmission).

As one example, the first DRB is used for EDT (Early Data Transmission).

As an embodiment, the first DRB is associated to a PDCP (Packet Data Convergence Protocol) entity.

As an embodiment, the first DRB is configured by an RRC message.

As an embodiment, the first DRB is configured by a SIB1 message.

As an embodiment, the first DRB is configured by a rrcreelease message.

For one embodiment, the first DRB is configured by an RRCConnectionRelease message.

As an embodiment, the first DRB includes a DRB configured to be recoverable in an RRC inactive state.

As an embodiment, the recovery means resume.

As an embodiment, the sentence "triggering the first status report as a response to the first condition set being satisfied" includes: triggering the first status report when the first set of conditions is satisfied.

As an embodiment, the sentence "triggering the first status report as a response to the first set of conditions being satisfied" includes: the first status report is triggered by the first set of states.

As one embodiment, the first RRC recovery procedure is used for an SDT procedure.

For one embodiment, the first RRC recovery procedure includes one RRC recovery procedure.

As an embodiment, the first RRC recovery procedure includes recovering a suspended RRC connection.

As one embodiment, the first RRC recovery procedure includes transmitting the first data block in an RRC inactive state.

For one embodiment, the phrase that the first RRC recovery procedure is being performed includes: a timer is running.

As a sub-embodiment of this embodiment, the one timer is not T319.

As a sub-embodiment of this embodiment, said one timer is started along with said first message.

As a sub-embodiment of this embodiment, the first timer is stopped when one RRC message is received and the one RRC message is a response to the first message.

As an additional embodiment of the sub-embodiment, the RRC message includes one of an rrcreelease message, or an rrcreesume message, or an RRCSetup message, or an RRCReject message, or an RRCConnectionRelease message, or an rrcconnectionresponse message, or an RRCConnectionSetup message, or an RRCConnectionReject message, or an rrccoarlydatacomplete message.

As an auxiliary embodiment of the sub-embodiment, the name of the RRC message includes at least one of RRC, connection, resume, release, RRCReject, setup, reconfiguration, complete, sdt, idt, inactive, small, data, and Transmission.

As a sub-embodiment of this embodiment, that the first timer is running means that the first timer is started and the count of the first timer does not reach the expiration value of the first timer.

As a sub-embodiment of this embodiment, the first timer is running.

As a sub-embodiment of this embodiment, that the first timer is running means that the timing of the first timer is not equal to 0 and not equal to the expiration value of the first timer.

For one embodiment, the phrase that the first RRC recovery procedure is being performed includes: a preamble sequence used for SDT is transmitted and is listening for a PDCCH scrambled by MSGB-RNTI or TEMPORARY _ C-RNTI or C-RNTI.

As one embodiment, the phrase that the first RRC recovery procedure is being performed includes: the pre-configured resources used for SDT are being used.

As an embodiment, the sentence "the first set of conditions includes that the first RRC recovery procedure is being performed and a first data block is validated" includes: the first set of conditions is satisfied when the first RRC recovery procedure is executing and a first data block is in effect.

As an embodiment, the sentence "the first set of conditions includes that the first RRC recovery procedure is being performed and a first data block takes effect" includes: at least the first RRC recovery procedure is executing and first data block validation is used to determine that the first set of conditions is satisfied.

As one embodiment, the phrase first data block validation comprises: the first data block is valid for a MAC entity (available to the MAC entry).

As one embodiment, the phrase first data block validation comprises: the first data block arrives at least one of a MAC layer or an RLC layer or a PDCP layer.

As one embodiment, the phrase first data block validation comprises: the first data block is ready to be transmitted.

As one embodiment, the phrase first data block validation comprises: the first data block is generated but no resources are allocated.

As one embodiment, the phrase associating the first data chunk to the first DRB includes: the first data block is mapped to the first DRB.

As one embodiment, the phrase associating the first data chunk to the first DRB includes: the first data block is not data of an SRB.

As an embodiment the dashed box F6.1 is optional.

As an embodiment, the dashed box F6.2 is optional.

As an embodiment, the dashed box F6.3 is optional.

As an example, the dashed box F6.1 exists.

As an example, the dashed box F6.1 is not present.

As an example, the dashed box F6.2 exists.

As an example, the dashed box F6.2 is not present.

As an example, the dashed box F6.3 exists.

As an example, the dashed box F6.3 is not present.

As an embodiment, one of said dashed box F6.2 and said dashed box F6.3 is present.

As an example, the dashed box F6.2 is present and the dashed box F6.3 is not present.

As an embodiment, the dashed box F6.2 is not present and the dashed box F6.3 is present.

Example 7

Embodiment 7 illustrates a schematic diagram of a first status report belonging to a first MAC subheader according to an embodiment of the present application, as shown in fig. 7. In fig. 7, a block indicates a MAC PDU or a MAC sub-header or a MAC SDU or a MAC CE or a padding or a field or fields; it is specifically noted that one block in this example indicates in another block that the other block includes the one block, and the size and position relationship of the one block and the other block does not limit the specific format of the first MAC PDU of the present application.

In embodiment 7, the first status report belongs to the first MAC subheader 702.

As an embodiment, the first transmitter, constructs a first MAC PDU 701; transmitting the first MAC PDU 701; the first MAC PDU 701 comprises a first MAC sub-PDU 702, the first MAC sub-PDU 702 comprises a first MAC sub-header 703, the first MAC sub-header 703 comprises at least a first field 704 and an LCID field 705, the first field 704 in the first MAC sub-header 703 is used to indicate whether the first MAC sub-PDU 702 comprises a first status report, the LCID field 705 of the first MAC sub-PDU 702 is used to indicate the first MAC payload; wherein the first field 704 is a field other than the LCID field 705 in the first MAC subheader 703; the first MAC load is not the first status report; the first status report belongs to the first MAC subheader 703.

As an embodiment, the first MAC subheader 703 includes the first status report field 706 therein, and the first status report field 706 includes the first status report.

As an embodiment, the first MAC subheader 703 further includes an elicid field therein.

As a sub-embodiment of this embodiment, the LCID field is set to 33 or 34.

For one embodiment, the first MAC subheader 703 does not include an etlcid field therein.

As a sub-embodiment of this embodiment, the LCID field is not set to 33 or 34.

As an embodiment, the first MAC subheader 703 further includes an R field therein.

For one embodiment, the first MAC subheader 703 does not include an R field.

As an embodiment, the first MAC subheader 703 further includes the second field in the present application.

As an embodiment, the second field in this application is not included in the first MAC subheader 703.

As an embodiment, the first MAC subheader 703 further includes a Format (Format) field therein.

As an embodiment, the first MAC subheader 703 does not include a Format (Format) field therein.

In one embodiment, the first MAC subheader 703 further includes a Length (L) field.

For one embodiment, the Length (L) field is not included in the first MAC subheader 703.

Example 8

Embodiment 8 illustrates a schematic diagram of a second MAC payload including a first status report according to an embodiment of the present application, as shown in fig. 8. In fig. 8, a block indicates a MAC PDU or a MAC sub-header or a MAC SDU or a MAC CE or a padding or a field or fields; it is specifically noted that one block in this example indicates in another block that the other block includes the one block, and the size and position relationship of the one block and the other block does not limit the specific format of the first MAC PDU of the present application.

In embodiment 8, the first MAC sub-PDU 802 comprises a second MAC payload comprising the first status report.

For one embodiment, the first transmitter, builds a first MAC PDU 801; transmitting the first MAC PDU 801; the first MAC PDU 801 comprises a first MAC sub-PDU 802, the first MAC sub-PDU 802 comprises a first MAC sub-header 803, the first MAC sub-header 803 comprises at least a first field 804 and an LCID field 805 therein, the first field 804 in the first MAC sub-header 803 is used to indicate whether the first MAC sub-PDU 802 comprises a first status report, the LCID field 805 of the first MAC sub-PDU 802 is used to indicate the first MAC payload; wherein the first field 804 is one field other than the LCID field 804 in the first MAC subheader 803; the first MAC load is not the first status report; the first MAC sub-PDU 802 includes a second MAC payload including the first status report.

As an embodiment, the phrase the first MAC sub-PDU 802 includes a second MAC payload including the first status report includes: the first MAC sub-PDU 802 includes a second MAC payload field 808, and the second MAC payload field 808 includes the first status report.

As an embodiment, the phrase the first MAC sub-PDU 802 includes a second MAC payload including the first status report includes: the first MAC sub-PDU 802 includes a second MAC payload field 808, the second MAC payload field 808 includes the first status report field 807, and the first status report field 807 includes the first status report.

As an embodiment, the first MAC subheader 803 further includes an elicid field therein.

As an embodiment, the first MAC subheader 803 does not include an etlcid field therein.

As an embodiment, a Reserved (R) field is further included in the first MAC subheader 803.

As an embodiment, a Reserved (R) field is not included in the first MAC subheader 803.

As an embodiment, the first MAC subheader 803 further includes the second field in the present application.

As an embodiment, the second field in this application is not included in the first MAC subheader 803.

As an embodiment, the first MAC subheader 803 further includes a Format (F) field therein.

As an embodiment, the first MAC subheader 803 does not include a Format (F) field.

As an embodiment, a Length (L) field is further included in the first MAC subheader 803.

As an embodiment, the Length (L) field is not included in the first MAC subheader 803.

Example 9

Embodiment 9 illustrates a schematic diagram of a format of a first MAC sub-PDU according to an embodiment of the present application, as shown in fig. 9. In fig. 9, ellipses indicate other MAC sub-PDUs of the first MAC PDU than the first MAC sub-PDU; a block indicates a MAC sub-PDU or a MAC sub-header or a MAC SDU or a MAC CE or a padding or a field or fields; it is specifically noted that one block in this example indicates in another block that the other block includes the one block, and the size and position relationship of the one block and the other block does not limit the specific format of the first MAC PDU of the present application.

In embodiment 9, said first MAC sub-PDU 901 comprises said first MAC sub-header 902 and said first MAC payload field 907; the first MAC subheader 902 includes the first field 905, the LCID field 906, and the first status report field 904; the first MAC load field 907 includes the first MAC load, and the first status report field 904 includes the first status report.

For one embodiment, the first field 905 in the first MAC subheader 902 is used to indicate that the first MAC subpdu 901 includes a first status report.

As an embodiment, the first transmitter, constructs a first MAC PDU; transmitting the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU 901, the first MAC sub-PDU 901 comprises a first MAC sub-header 902, the first MAC sub-header 902 comprises at least a first field 905 and an LCID field 906, the first field 905 in the first MAC sub-header 902 is used to indicate that the first MAC sub-PDU 901 comprises a first status report, the LCID field 906 of the first MAC sub-PDU 901 is used to indicate the first MAC payload; wherein the first field 905 is a field other than the LCID field 906 in the first MAC subheader 902; the first MAC loads the first status report 904; the first status report belongs to the first MAC subheader 902.

As an embodiment, the ellipses on the left side of the first MAC sub-PDU 901 do not exist, and the ellipses on the right side of the first MAC sub-PDU 901 exist.

As an embodiment, an ellipsis exists on the left side of the first MAC sub-PDU 901, and an ellipsis does not exist on the right side of the first MAC sub-PDU 901.

As an embodiment, both the ellipses on the left side of the first MAC sub-PDU 901 and the ellipses on the right side of the first MAC sub-PDU 901 exist.

As an embodiment, neither the ellipsis on the left side of the first MAC sub-PDU 901 nor the ellipsis on the right side of the first MAC sub-PDU 901 exists.

For one embodiment, the first MAC payload field 907 indicates the first MAC payload.

As an embodiment, the first MAC payload field 907 carries the first MAC payload.

For one embodiment, the first MAC payload field 907 includes the first MAC payload.

For one embodiment, the first status report field 904 indicates the first status report.

For an embodiment, the first status report field 904 carries the first status report.

For one embodiment, the first status report is included in the first status report field 904.

For one embodiment, the field in the first MAC subheader 902 is included in block 903.

For an embodiment, said block 903 includes at least said first field 905, said LCID field 906 and said first status report field 904.

For one embodiment, the block 903 further includes an etlcid field.

As an example, the eLCID field is not included in the block 903.

As an embodiment, a Reserved (R) field is also included in the block 903.

As an embodiment, a Reserved (R) field is not included in the block 903.

As an embodiment, the block 903 further includes the second field in this application.

As an example, the second field in this application is not included in the block 903.

As an embodiment, the block 903 further includes a Format (F) field.

As an embodiment, the Format (F) field is not included in the block 903.

In one embodiment, the block 903 further includes a Length (L) field.

As an example, the Length (L) field is not included in the block 903.

Example 10

Embodiment 10 illustrates a schematic diagram of a format of a first MAC sub-PDU according to another embodiment of the present application, as shown in fig. 10. In fig. 10, ellipses indicate other MAC sub-PDUs except the first MAC sub-PDU among the first MAC PDUs; a block indicates a MAC sub-PDU or a MAC sub-header or a MAC SDU or a MAC CE or a padding or a field or fields; it is specifically noted that one block in this example indicates in another block that the other block includes the one block, and the size and position relationship of the one block and the other block does not limit the specific format of the first MAC PDU of the present application.

In embodiment 10, the first MAC sub-PDU 1001 includes the first MAC sub-header 1002, the second MAC load domain 1006, and the first MAC load domain 1009; the first MAC subheader 1002 includes the first field 1004 and the LCID field 1005 therein; the second MAC loading domain 1006 includes the first status report domain 1008, the second MAC loading domain 1006 includes the second MAC loading, the first MAC loading domain 1009 includes the first MAC loading, and the first status report domain 1008 includes the first status report.

For one embodiment, the first field 1004 in the first MAC subheader 1002 is used to indicate that the first MAC subpdu 1001 includes a first status report.

As an embodiment, the first transmitter, constructs a first MAC PDU; transmitting the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU 1001, the first MAC sub-PDU 1001 comprises a first MAC sub-header 1002, the first MAC sub-header 1002 comprises at least a first field 1004 and an LCID field 1005, the first field 1004 in the first MAC sub-header 1002 is used to indicate that the first MAC sub-PDU 1001 comprises a first status report, the LCID field 1005 of the first MAC sub-PDU 1001 is used to indicate the first MAC payload; wherein the first field 1004 is one field other than the LCID field 1005 in the first MAC subheader 1002; the first MAC load is not the first status report; the first MAC sub-PDU 1001 includes a second MAC payload, which includes the first status report.

As an embodiment, the ellipses on the left side of the first MAC sub-PDU 1001 do not exist, and the ellipses on the right side of the first MAC sub-PDU 1001 exist.

As an embodiment, an ellipsis exists on the left side of the first MAC sub-PDU 1001 and an ellipsis does not exist on the right side of the first MAC sub-PDU 1001.

As an embodiment, both the ellipses on the left side of the first MAC sub-PDU 1001 and the ellipses on the right side of the first MAC sub-PDU 1001 exist.

As an embodiment, neither the ellipsis on the left side of the first MAC sub-PDU 1001 nor the ellipsis on the right side of the first MAC sub-PDU 1001 exist.

For one embodiment, the first MAC load field 1009 indicates the first MAC load.

For an embodiment, the first MAC payload field 1009 carries the first MAC payload.

For one embodiment, the first MAC payload field 1009 includes the first MAC payload.

For one embodiment, the second MAC payload field 1006 indicates the second MAC payload.

As an embodiment, the second MAC payload domain 1006 carries the second MAC payload.

For one embodiment, the second MAC payload domain 1006 includes the second MAC payload.

For one embodiment, the first status report field 1008 indicates the first status report.

As an embodiment, the first status report field 1008 carries the first status report.

For one embodiment, the first status report is included in the first status report field 1008.

For one embodiment, the field in the first MAC subheader 1002 is included in block 1003.

In one embodiment, said block 1003 includes at least said first field 1004 and said LCID field 1005.

For one embodiment, the block 1003 further includes an etlcid field.

For one embodiment, the eLCID field is not included in block 1003.

As an embodiment, the block 1003 further includes a Reserved (R) field.

As an embodiment, a Reserved (R) field is not included in the block 1003.

As an embodiment, the block 1003 further includes the second field in this application.

As an embodiment, the second field in this application is not included in the block 1003.

For one embodiment, the block 1003 further includes a Format (F) field.

For one embodiment, the block 1003 does not include a Format (F) field.

In one embodiment, the block 1003 further includes a Length (L) field.

For one embodiment, the Length (L) field is not included in the block 1003.

For one embodiment, block 1007 includes a field in the second MAC payload field.

For one embodiment, the block 1007 includes at least the first status reporting field.

As an embodiment, the block 1007 also includes other fields in the present application.

As an example, other fields in the present application are not included in the block 1007.

Example 11

Embodiment 11 illustrates a schematic diagram of a format of a first MAC sub-PDU according to still another embodiment of the present application, as shown in fig. 11. In fig. 11, ellipses indicate other MAC sub-PDUs of the first MAC PDU than the first MAC sub-PDU; a block indicates a MAC sub-PDU or a MAC sub-header or a MAC SDU or a MAC CE or a padding or a field or fields; it is specifically noted that one block in this example indicates in another block that the other block includes the one block, and the size and position relationship of the one block and the other block does not limit the specific format of the first MAC PDU of the present application.

In embodiment 11, the first MAC sub-PDU 1101 includes the first MAC sub-header 1102 and the first MAC payload field 1106; the first MAC subheader 1102 comprises the first field 1104 and the LCID field 1105; the first MAC payload is included in the first MAC payload domain 1106.

For one embodiment, the first field 1104 in the first MAC subheader 1102 is used to indicate that the first MAC subpdu 1101 does not include a first status report.

As an embodiment, the first transmitter, constructs a first MAC PDU; transmitting the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU 1101, the first MAC sub-PDU 1101 comprises a first MAC sub-header 1102, the first MAC sub-header 1102 comprises at least a first field 1104 and an LCID field 1105 therein, the first field 1104 in the first MAC sub-header 1102 is used to indicate that the first MAC sub-PDU 1101 does not comprise a first status report, the LCID field 1105 of the first MAC sub-PDU 1101 is used to indicate the first MAC load; wherein the first field 1104 is a field other than the LCID field 1105 in the first MAC subheader 1102; the first MAC load is not the first status report.

As a sub-embodiment of this embodiment, when the first field 1104 in the first MAC subheader 1102 is used to indicate that the first MAC subpdu 1101 includes a first status report, the first status report belongs to the first MAC subheader 1102.

As a sub-embodiment of this embodiment, when the first field 1104 in the first MAC subheader 1102 is used to indicate that the first MAC subpdu 1101 includes a first status report, the first MAC subpdu 1101 includes a second MAC payload including the first status report.

As an embodiment, the ellipses on the left side of the first MAC sub-PDU 1101 are not present, and the ellipses on the right side of the first MAC sub-PDU 1101 are present.

As an example, the ellipses on the left side of the first MAC sub-PDU 1101 exist, and the ellipses on the right side of the first MAC sub-PDU 1101 do not exist.

As an example, both the ellipses on the left side of the first MAC sub-PDU 1101 and the ellipses on the right side of the first MAC sub-PDU 1101 exist.

As an example, neither the ellipsis to the left of the first MAC sub-PDU 1101 nor the ellipsis to the right of the first MAC sub-PDU 1101 exists.

For one embodiment, the first MAC load domain 1106 indicates the first MAC load.

As an embodiment, the first MAC payload domain 1106 carries the first MAC payload.

For one embodiment, the first MAC payload is included in the first MAC payload domain 1106.

For one embodiment, block 1103 includes a field in the first MAC subheader 1102.

For one embodiment, the block 1103 includes at least the first field 1104 and the LCID field 1105.

For one embodiment, the block 1103 further includes an etlcid field.

For one embodiment, the eLCID field is not included in block 1103.

For one embodiment, the block 1103 further includes a Reserved (R) field.

For one embodiment, the Reserved (R) field is not included in the block 1103.

For one embodiment, the block 1103 further includes the second field of the present application.

For one embodiment, the second field in this application is not included in the block 1103.

For one embodiment, the block 1103 further includes a Format (F) field.

As an embodiment, the Format (F) field is not included in the block 1103.

For one embodiment, the block 1103 further includes a Length (L) field.

For one embodiment, the Length (L) field is not included in the block 1103.

Example 12

Embodiment 12 illustrates a schematic diagram of a first MAC subheader according to a first embodiment of the present application, as shown in fig. 12. In fig. 12, one block represents one domain or a plurality of domains.

In embodiment 12, the first MAC subheader includes the first domain 1202, the LCID domain 1201, the second domain 1204, the target domain 1205, and an R domain 1203; or the first MAC subheader includes the first domain 1202, the LCID domain 1201, the second domain 1204, and the R domain 1203; wherein the first status report belongs to the first MAC subheader.

As one embodiment, the target field 1205 is always present.

The target field 1205 is optional as an embodiment.

As one embodiment, the target field 1205 is present.

As a sub-implementation of this embodiment, the first MAC subheader includes the first field 1202, the LCID field 1201, the second field 1204, the target field 1205, and the R field 1203.

As a sub-implementation of this embodiment, the first MAC subheader is composed of the first domain 1202, the LCID domain 1201, the second domain 1204, the target domain 1205, and the R domain 1203.

As a sub-implementation of this embodiment, when the first domain 1202 is set to the first target value, the first MAC subheader is composed of the first domain 1202, the LCID domain 1201, the second domain 1204, the target domain 1205, and the R domain 1203.

For one embodiment, the target field 1205 is not present.

As a sub-implementation of this embodiment, the first MAC subheader includes the first field 1202, the LCID field 1201, the second field 1204, and the R field 1203.

As a sub-implementation of this embodiment, the first MAC subheader is composed of the first domain 1202, the LCID domain 1201, the second domain 1204, and the R domain 1203.

As a sub-implementation of this embodiment, when the first field 1202 is set to a second target value, the first MAC subheader is composed of the first field 1202, the LCID field 1201, the second field 1204, and the R field 1203.

As an embodiment, the R domain 1203, the first domain 1202, and the LCID domain 1201 occupy a first byte (Oct 1), and a sum of lengths of the R domain, the first domain 1202, and the LCID domain 1201 is equal to one byte.

As an embodiment, the second field 1204 occupies a second byte (Oct 2), and the length of the second field 1204 is equal to one byte.

As an embodiment, when the target field 1205 exists, the target field 1205 occupies the third byte (Oct 3), and the length of the target field 1205 is equal to one byte.

For one embodiment, the second field 1204 is equal to one byte in length.

As an example, the second domain 1204 is placed directly after the LCID domain.

For one embodiment, the target domain 1205 is placed directly after the LCID domain.

As an example, the R domain 1203 is placed directly before the first domain 1202.

As one embodiment, the first domain 1202 is placed directly before the R domain 1203.

As an embodiment, the R field 1203 is the highest bit in the first MAC subheader.

As an embodiment, the first domain 1202 is placed directly after the R domain and before the LCID domain.

Example 13

Embodiment 13 illustrates a schematic diagram of a first MAC subheader according to a second embodiment of the present application, as shown in fig. 13. In fig. 13, one block represents one domain or a plurality of domains.

In embodiment 13, the first MAC subheader includes the first field 1302, the LCID field 1301, the second field 1303, the second field 1304, and the destination field 1305; or the first MAC subheader includes the first field 1302, the LCID field 1301, the second field 1303, and the second field 1304; wherein the first status report belongs to the first MAC subheader.

The target domain 1305 is always present, as one embodiment.

For one embodiment, the target domain 1305 is optional.

For one embodiment, the target domain 1305 is present.

As a sub-implementation of this embodiment, the first MAC subheader includes the first field 1302, the LCID field 1301, the second field 1303, the second field 1304, and the destination field 1305.

As a sub-implementation of this embodiment, the first MAC subheader is composed of the first field 1302, the LCID field 1301, the second field 1303, the second field 1304, and the target field 1305.

As a sub-implementation of this embodiment, when the first field 1302 is set to a first target value, the first MAC subheader is composed of the first field 1302, the LCID field 1301, the second field 1303, the second field 1304, and the target field 1305.

For one embodiment, the target domain 1305 is not present.

As a sub-implementation of this embodiment, the first MAC subheader includes the first field 1302, the LCID field 1301, the second field 1303, and the second field 1304.

As a sub-implementation of this embodiment, the first MAC subheader is composed of the first field 1302, the LCID field 1301, the second field 1303, and the second field 1304.

As a sub-implementation of this embodiment, when the first field 1302 is set to a second target value, the first MAC subheader is composed of the first field 1302, the LCID field 1301, the second field 1303, and the second field 1304.

As an embodiment, the second field 1303, the first field 1302, and the LCID field 1301 occupy a first byte (Oct 1), and the sum of the lengths of the second field 1303, the first field 1302, and the LCID field 1301 is equal to one byte.

As an example, the second field 1304 occupies a second byte (Oct 2), and the length of the second field 1304 is equal to one byte.

For one embodiment, when the destination field 1305 is present, the destination field 1305 occupies the third byte (Oct 3), and the length of the destination field 1305 is equal to one byte.

As an embodiment, the second field 1303 and the second field 1304 together form a field.

As an embodiment, the second domain 1303 and the second domain 1304 are the same domain.

As an embodiment, the sum of the lengths of the second field 1303 and the second field 1304 is equal to 9 bits.

As an embodiment, the first domain 1302 is placed directly after the second domain 1303.

As an embodiment, the second field 1303 is placed directly after the first field 1302.

Example 14

Embodiment 14 illustrates a schematic diagram of a first MAC subheader according to a third embodiment of the present application, as shown in fig. 14. In fig. 14, one block represents one domain or a plurality of domains.

In embodiment 14, the first MAC subheader includes an R field 1403, a first field 1402, an LCID field 1401, and a target field 1404; or the first MAC subheader includes an R field 1403, a first field 1402 and an LCID field 1401; wherein the first status report belongs to the first MAC subheader.

As one embodiment, the target domain 1404 always exists.

The target field 1404 is optional as an embodiment.

As one embodiment, the target domain 1404 exists.

As a sub-embodiment of this embodiment, the first MAC subheader includes an R field 1403, a first field 1402, an LCID field 1401, and a target field 1404.

As a sub-embodiment of this embodiment, the first MAC subheader is composed of an R field 1403, a first field 1402, an LCID field 1401, and a target field 1404.

As a sub-embodiment of this embodiment, when the first field 1402 is set to a first target value, the first MAC subheader is composed of an R field 1403, the first field 1402, an LCID field 1401, and a target field 1404.

For one embodiment, the target domain 1404 does not exist.

As a sub-embodiment of this embodiment, the first MAC subheader includes an R field 1403, a first field 1402, and an LCID field 1401.

As a sub-embodiment of this embodiment, the first MAC subheader is composed of an R field 1403, a first field 1402, and an LCID field 1401.

As a sub-embodiment of this embodiment, when the first field 1402 is set to the second target value, the first MAC sub-header is composed of an R field 1403, a first field 1402, and an LCID field 1401.

As an embodiment, the R field 1403, the first field 1402, and the LCID field 1401 occupy a first byte (Oct 1), and a sum of lengths of the R field 1403, the first field 1402, and the LCID field 1401 is equal to one byte.

As an example, when the target field 1404 exists, the target field 1404 occupies a third byte (Oct 2), and the length of the target field 1404 is equal to one byte.

As an embodiment, the first field 1402 is placed directly after the R field 1403.

As an example, the R-field 1403 is placed directly after the first field 1402.

Example 15

Embodiment 15 illustrates a schematic diagram of a first MAC subheader according to a fourth embodiment of the present application, as shown in fig. 15. In fig. 15, one block represents one domain or a plurality of domains; the first field 1502 and LCID field 1501 occupy the first byte (Oct 1), and the sum of the lengths of the first field 1502 and LCID field 1501 is equal to one byte; the target field 1503 occupies the second byte (Oct 2), and the length of the target field 1503 is equal to one byte.

In embodiment 15, the first MAC subheader includes a first field 1502, an LCID field 1501 and a destination field 1503; or the first MAC subheader comprises a first field 1502 and an LCID field 1501; wherein the first status report belongs to the first MAC subheader.

For one embodiment, the first field 1502 is equal to 2 bits in length.

As one embodiment, the target domain 1503 always exists.

The target domain 1503 is optional as an embodiment.

As an embodiment, the target domain 1503 exists.

As a sub-embodiment of this embodiment, the first MAC subheader includes the first field 1502, the LCID field 1501 and the target field 1503.

As a sub-embodiment of this embodiment, the first MAC subheader is composed of the first field 1502, the LCID field 1501 and the target field 1503.

As a sub-embodiment of this embodiment, when the first field 1502 is set to a first target value, the first MAC subheader is composed of the first field 1502, the LCID field 1501, and the target field 1503.

As an embodiment, the target domain 1503 does not exist.

As a sub-embodiment of this embodiment, the first MAC subheader includes the first field 1502 and the LCID field 1501 therein.

As a sub-embodiment of this embodiment, the first MAC subheader is composed of the first field 1502 and the LCID field 1501.

As a sub-embodiment of this embodiment, when the first field 1502 is set to a second target value, the first MAC sub-header is composed of the first field 1502 and the LCID field 1501.

Example 16

Embodiment 16 illustrates a schematic diagram of a first MAC subheader according to a fifth embodiment of the present application, as shown in fig. 16. In fig. 16, one block represents one domain or a plurality of domains.

In embodiment 16, the first MAC subheader includes at least a first field 1602, an LCID field 1601, and an R field 1603.

As an embodiment, the R field 1603, the first field 1602 and the LCID field 1601 occupy a first byte (Oct 1), and the sum of the lengths of the R field 1603, the first field 1602 and the LCID field 1601 is equal to one byte.

As an embodiment, the first MAC subheader includes the first field 1602, the LCID field 1601, the second field 1604, and the R field 1603; wherein the first MAC sub-PDU includes the second MAC payload, which includes the first status report.

As a sub-embodiment of this embodiment, the second domain 1604 exists.

As a sub-embodiment of this embodiment, the first MAC subheader is composed of the first field 1602, the LCID field 1601, the second field 1604, and the R field 1603.

As a sub-embodiment of this embodiment, the length indicated by the second field 1604 comprises the second MAC payload field.

As a sub-embodiment of this embodiment, the length indicated by the second field 1604 does not include the second MAC payload field.

As a sub-embodiment of this embodiment, the length of the second field is independent of the first field 1602.

As a sub-embodiment of this embodiment, the second field 1604 occupies a second byte (Oct 2), and the length of the second field 1604 is equal to one byte.

As an embodiment, the first MAC subheader includes the first field 1602, the LCID field 1601, and the R field 1603; wherein the first MAC sub-PDU includes the second MAC payload, which includes the first status report.

As a sub-embodiment of this embodiment, the second domain 1604 is not present.

As a sub-embodiment of this embodiment, the first MAC subheader is composed of the first field 1602, the LCID field 1601, and the R field 1603.

As an example, the R field 1603 is placed directly before the first field 1602.

As an example, the first field 1602 is placed directly before the R field 1603.

Example 17

Embodiment 17 illustrates a schematic diagram of a first MAC subheader according to a sixth embodiment of the present application, as shown in fig. 17. In fig. 17, one block represents one domain or a plurality of domains.

In embodiment 17, the first MAC subheader includes a first field 1704, a second field 1703, a first field 1702, and an LCID field 1701; wherein the first MAC sub-PDU comprises a second MAC payload comprising the first status report.

For one embodiment, the first MAC subheader consists of the first field 1704, the second field 1703, the first field 1702, and the LCID field 1701.

As an embodiment, the second field 1703, the first field 1702, and the LCID field 1701 occupy a first byte (Oct 1), and the sum of the lengths of the second field 1703, the first field 1702, and the LCID field 1701 is equal to one byte.

As an example, the second field 1704 occupies a second byte (Oct 2), and the length of the second field 1704 is equal to one byte.

For one embodiment, the second domain 1703 and the second domain 1704 together form a domain.

For one embodiment, the second domain 1703 and the second domain 1704 are the same domain.

For one embodiment, the sum of the lengths of the second field 1703 and the second field 1704 is equal to 9 bits.

For one embodiment, the lengths indicated by the second field 1703 and the second field 1704 comprise the second MAC payload field.

For one embodiment, the lengths indicated by the second field 1703 and the second field 1704 do not include the second MAC payload field.

Example 18

Embodiment 18 illustrates a schematic diagram of a first MAC subheader according to a seventh embodiment of the present application, as shown in fig. 18. In fig. 18, one block represents one domain or a plurality of domains.

In embodiment 18, the first MAC subheader includes an LCID field 1801, an F field 1802, a first field 1803, a second field 1804, a second field 1805, and a target field 1806; or the first MAC subheader includes LCID field 1801, F field 1802, first field 1803 and second field 1804; or the first MAC subheader includes LCID field 1801, F field 1802, first field 1803, second field 1804, and second field 1805; or the first MAC subheader includes an LCID field 1801, an F field 1802, a first field 1803, a second field 1804, and a target field 1806.

As one embodiment, the target domain 1806 is always present.

For one embodiment, the target domain 1806 is optional.

As an embodiment, the target domain 1806 exists.

As an embodiment, the target domain 1806 is not present.

As an embodiment, the second field 1805 is optional.

As an embodiment, the second domain 1805 exists.

As an example, the second domain 1805 is not present.

As an embodiment, both said target domain 1806 and said second domain 1805 are present.

As a sub-embodiment of this embodiment, the first status report belongs to the first MAC subheader.

As a sub-embodiment of this embodiment, the first MAC subheader is composed of the LCID field 1801, the F field 1802, the first field 1803, the second field 1804, the second field 1805, and the target field 1806.

As a sub-embodiment of this embodiment, when the first field 1803 is set to the first target value and the F field is set to 1, the first MAC subheader is composed of the LCID field 1801, the F field 1802, the first field 1803, the second field 1804, the second field 1805, and the target field 1806.

As an example, neither the target domain 1806 nor the second domain 1805 is present.

As a sub-embodiment of this embodiment, the first MAC sub-PDU comprises a second MAC payload, the second MAC payload comprising the first status report.

As a sub-embodiment of this embodiment, the first MAC subheader is composed of the LCID field 1801, the F field 1802, the first field 1803, and the second field 1804.

As a sub-embodiment of this embodiment, when the first field 1803 is set to the second target value and the F field is set to 0, the first MAC subheader is composed of the LCID field 1801, the F field 1802, the first field 1803, and the second field 1804.

As an embodiment, the target domain 1806 exists and the second domain 1805 does not exist.

As a sub-embodiment of this embodiment, the first MAC subheader is composed of the LCID field 1801, the F field 1802, the first field 1803, the second field 1804, and the target field 1806.

As a sub-embodiment of this embodiment, when the first field 1803 is set to the first target value and the F field is set to 0, the first MAC subheader is composed of the LCID field 1801, the F field 1802, the first field 1803, the second field 1804, and the target field 1806.

As an embodiment, the target domain 1806 does not exist and the second domain 1805 exists.

As a sub-embodiment of this embodiment, the first MAC subheader is composed of the LCID field 1801, the F field 1802, the first field 1803, the second field 1804, and the second field 1805.

As a sub-embodiment of this embodiment, when the first field 1803 is set to the second target value and the F field is set to 1, the first MAC subheader is composed of the LCID field 1801, the F field 1802, the first field 1803, the second field 1804, and the second field 1805.

As an embodiment, the F field 1802, the first field 1803, and the LCID field 1801 occupy a first byte (Oct 1), and a sum of lengths of the F field 1802, the first field 1803, and the LCID field 1801 is equal to one byte.

As an embodiment, when the second field 1805 exists, the second field 1805 occupies a third byte (Oct 3), and the length of the second field 1805 is equal to 1 byte.

As an embodiment, when the second field 1805 exists, the second field 1804 and the second field 1805 occupy a second byte (Oct 2) and a third byte (Oct 3), and the sum of the lengths of the second field 1804 and the second field 1805 is equal to 2 bytes.

As an embodiment, when the target field 1806 exists, the target field 1806 occupies a third byte (Oct 3) or a fourth byte (Oct 4), and the length of the target field 1806 is equal to one byte.

Example 19

Embodiment 19 illustrates a schematic diagram of a first MAC subheader according to an eighth embodiment of the present application, as shown in fig. 19. In fig. 19, one block represents one domain or a plurality of domains.

In embodiment 19, the first MAC subheader includes a second field 1903, a first field 1902, and an LCID field 1901; wherein the first MAC sub-PDU comprises a second MAC payload comprising the first status report. .

For an embodiment, the first MAC subheader is composed of the second field 1903, the first field 1902, and the LCID field 1901.

As an embodiment, the first field 1902 and the LCID field 1901 occupy a first byte (Oct 1), and the sum of the lengths of the first field 1902 and the LCID field 1901 is equal to one byte; the second field 1903 occupies a second byte (Oct 2)

As an example, the first field 1902 may have a length equal to 2 bits.

Example 20

Embodiment 20 illustrates a schematic diagram of a first MAC load and a second MAC load according to an embodiment of the present application, as shown in fig. 20. In fig. 20, one block represents one domain or a plurality of domains.

In embodiment 20, the first MAC sub-PDU includes a first MAC payload domain 2002 and a second MAC payload domain 2001, the second MAC payload domain 2001 is directly placed before the first MAC payload domain 2002, the first MAC payload domain 2002 includes the first MAC payload, the second MAC payload domain 2001 includes the second MAC payload, and the second MAC payload includes the first status report.

As an embodiment, the second MAC payload domain 2001 always exists.

As an embodiment, the second MAC payload domain 2001 is optional.

As a sub-embodiment of this embodiment, the second MAC payload field 2001 exists when the first field in the first MAC subheader is used to indicate that the first MAC subpdu includes the first status report.

As a sub-embodiment of this embodiment, the second MAC payload domain 2001 does not exist when the first field in the first MAC subheader is used to indicate that the first MAC subpdu does not include the first status report.

Example 21

Embodiment 21 illustrates a schematic diagram of a first MAC load and a second MAC load according to another embodiment of the present application, as shown in fig. 21. In fig. 21, one block represents one domain or a plurality of domains.

In embodiment 21, the first MAC sub-PDU includes a first MAC load domain 2101 and a second MAC load domain 2102, where the second MAC load domain 2102 is directly placed before the first MAC load domain 2101, the first MAC load domain 2101 includes the first MAC load, the second MAC load domain 2102 includes the second MAC load, and the second MAC load includes the first status report.

As an example, the second MAC payload domain 2102 always exists.

For one embodiment, the second MAC payload domain 2102 is optional.

As a sub-embodiment of this embodiment, the second MAC payload field 2102 exists when the first field in the first MAC subheader is used to indicate that the first MAC subpdu includes the first status report.

As a sub-embodiment of this embodiment, the second MAC payload field 2102 is absent when the first field in the first MAC subheader is used to indicate that the first MAC subpdu does not include the first status report.

Example 22

Embodiment 22 illustrates a block diagram of a processing apparatus for use in a first node according to one embodiment of the present application; as shown in fig. 22. In fig. 22, the processing means 2200 in the first node comprises a first receiver 2201 and a first transmitter 2202.

A first transmitter 2202 that constructs a first MAC PDU; transmitting the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload;

in embodiment 22, the first field is a field other than the LCID field in the first MAC subheader; the first MAC payload is not the first status report.

As an embodiment, the first status report belongs to the first MAC subheader.

As one embodiment, the first MAC sub-PDU includes a second MAC payload including the first status report.

As an embodiment, a second field is included in the first MAC subheader, the second field indicating a length of the first MAC payload.

As an embodiment, the first transmitter 2202, transmits a first message; recovering at least a first DRB along with the first message; triggering the first status report in response to a first set of conditions being satisfied; wherein the first message is used for a first RRC recovery procedure; the first set of conditions includes that the first RRC recovery procedure is executing and a first data block is in effect, the first data block associated with the first DRB; the first status report indicates a cache coherency state.

For one embodiment, the first receiver 2201 receives first signaling used to determine whether the first field is used to indicate whether the first MAC sub-PDU includes a first status report.

For one embodiment, the first receiver 2201 includes the antenna 452, the receiver 454, the multi-antenna receive processor 458, the receive processor 456, the controller/processor 459, the memory 460, and the data source 467 of fig. 4.

For one embodiment, the first receiver 2201 includes the antenna 452, the receiver 454, the multi-antenna receive processor 458, and the receive processor 456 of fig. 4.

For one embodiment, the first receiver 2201 includes the antenna 452, the receiver 454, and the receiving processor 456 of fig. 4.

The first transmitter 2202 includes, for one embodiment, the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, the transmit processor 468, the controller/processor 459, the memory 460, and the data source 467 of fig. 4 of the present application.

The first transmitter 2202 includes, as one example, the antenna 452, the transmitter 454, the multi-antenna transmit processor 457, and the transmit processor 468 of fig. 4 of the present application.

For one embodiment, the first transmitter 2202 includes the antenna 452, the transmitter 454, and the transmitting processor 468 of fig. 4.

Example 23

Embodiment 23 illustrates a block diagram of a processing apparatus for use in a second node according to an embodiment of the present application; as shown in fig. 23. In fig. 23, the processing means 2300 in the second node comprises a second transmitter 2301 and a second receiver 2302.

A second receiver 2302 that receives the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload;

in embodiment 23, the first MAC PDU is constructed; the first domain is one of the first MAC subheader except the LCID domain; the first MAC payload is not the first status report.

As an embodiment, the first status report belongs to the first MAC subheader.

For one embodiment, the second receiver 2302 receives a first message; wherein at least a first DRB is resumed along with the first message; in response to a first set of conditions being met, the first status report is triggered; the first message is used for a first RRC recovery procedure; the first set of conditions includes that the first RRC recovery procedure is being performed and a first data block is in effect, the first data block being associated with the first DRB; the first status report indicates a cache coherency state.

For one embodiment, the second transmitter 2301 transmits a first signaling used to determine whether the first field is used to indicate whether the first MAC sub-PDU includes a first status report.

The second transmitter 2301 includes, for one embodiment, the antenna 420, the transmitter 418, the multi-antenna transmit processor 471, the transmit processor 416, the controller/processor 475, and the memory 476 of fig. 4.

For one embodiment, the second transmitter 2301 includes the antenna 420, the transmitter 418, the multi-antenna transmit processor 471 and the transmit processor 416 of fig. 4.

For one embodiment, the second transmitter 2301 includes the antenna 420, the transmitter 418, and the transmit processor 416 of fig. 4.

For one embodiment, the second receiver 2302 includes the antenna 420, the receiver 418, the multi-antenna receive processor 472, the receive processor 470, the controller/processor 475, and the memory 476 of fig. 4 of the present application.

For one embodiment, the second receiver 2302 includes the antenna 420, the receiver 418, the multi-antenna receive processor 472, and the receive processor 470 shown in fig. 4.

For one embodiment, the second receiver 2302 includes the antenna 420, the receiver 418, and the receive processor 470 shown in fig. 4.

Example 24

Embodiment 24 illustrates a schematic diagram of a target domain or a second MAC payload domain according to an embodiment of the present application, as shown in fig. 24. In fig. 24, one block represents one domain or a plurality of domains; the sum of the lengths of the first status report field 2402 and the other fields 2401 is equal to 1 byte.

In embodiment 24, the first MAC subheader includes the first status report field 2402 and other fields 2401, and the first status report field 2402 includes the first status report.

As an embodiment, the other field 2401 is placed directly before the first status reporting field 2402.

As an example, the other field 2401 is placed directly after the first status reporting field 2402.

In embodiment 24, the first status reporting field is used to indicate the first status report, the length of the first status reporting field is equal to L1 bits, and the L1 is not greater than the L0.

For one embodiment, the first status reporting field 2402 is a MAC field.

As an example, the L1 is equal to the L0.

As an embodiment, the L1 is smaller than the L0.

As an example, said L1 is equal to 8.

As an example, said L1 is equal to 7.

As an example, said L1 is equal to 6.

As an example, said L1 is equal to 5.

As an example, said L1 is equal to 4.

As an example, said L1 is equal to 3.

As an example, L1 is equal to 2.

As an example, L1 is equal to 1.

As an example, fig. 24 illustrates the target domain.

As an additional embodiment of this sub-embodiment, the first status reporting domain is one of the target domains.

As an adjunct embodiment of this sub-embodiment, the target field consists of the first status reporting field 2402 and the other field 2401.

As an adjunct embodiment to this sub-embodiment, the target domain does not include other domains 2401.

As a lower embodiment of this dependent embodiment, the target field is composed of the first status reporting field 2402.

As a lower embodiment of this dependent embodiment, the target domain comprises only one MAC domain.

As an adjunct embodiment of this sub-embodiment, the target domain includes another domain 2401, and the other domain 2401 is different from the first status reporting domain 2402.

As a lower embodiment of this dependent embodiment, the length of the other field 2401 is equal to the difference between the length of the target field and the length of the first status report field 2402.

As a lower embodiment of this subordinate embodiment, the target domain is composed of the first status reporting domain 2402 and the other domain 2401.

As a lower embodiment of the dependent embodiment, the first status reporting field 2402 and the other field 2401 are used to indicate uplink data amount and power headroom, respectively.

As a lower embodiment of this subsidiary embodiment, the first status report field 2402 and the other field 2401 are used to indicate uplink data volume and listen before talk failure, respectively.

As a lower embodiment of the dependent embodiment, the first status report field 2402 and the other field 2401 are used to indicate uplink data amount and beam failure, respectively.

As a lower embodiment of the dependent embodiment, the first status report field 2402 is used to indicate an uplink data amount, and the other field 2401 is an R field.

As a lower embodiment of this subordinate embodiment, the other domain 2401 includes an R domain.

As a subordinate embodiment of this subordinate embodiment, the other domain 2401 includes at least one MAC domain.

As an example, fig. 24 illustrates the second MAC payload field.

As an additional embodiment of this sub-embodiment, the first status reporting domain is one of the second MAC payload domains.

As an additional embodiment of this sub-embodiment, the second MAC payload field is composed of the first status report field 2402 and the other field 2401.

As an adjunct embodiment of this sub-embodiment, no other field 2401 is included in the second MAC payload field.

As a lower embodiment of this dependent embodiment, the second MAC payload field is composed of the first status reporting field 2402.

As a lower embodiment of this dependent embodiment, the second MAC payload field comprises only one MAC field.

As an auxiliary embodiment of this sub-embodiment, the second MAC payload field includes another field 2401, and the another field 2401 is different from the first status report field 2402.

As a lower embodiment of the dependent embodiment, the length of the other field 2401 is equal to the difference between the length of the second MAC payload field and the length of the first status reporting field 2402.

As a lower embodiment of the dependent embodiment, the second MAC payload field is composed of the first status report field 2402 and the other field 2401.

As a lower embodiment of the dependent embodiment, the first status report field 2402 and the other field 2401 are used to indicate an uplink data amount and a power headroom, respectively.

As a lower embodiment of the dependent embodiment, the first status reporting field 2402 and the other field 2401 are used to indicate an uplink data amount and an R field, respectively.

As a lower embodiment of this dependent embodiment, the other domain 2401 includes at least one MAC domain.

For one embodiment, the target domain and the second MAC payload domain do not exist simultaneously.

As an embodiment, the target domain is present and the second MAC payload domain is absent.

As an embodiment, the target domain does not exist and the second MAC payload domain exists.

It will be understood by those skilled in the art that all or part of the steps of the above methods may be implemented by a program instructing relevant hardware, and the program may be stored in a computer-readable storage medium, such as a read-only memory, a hard disk, or an optical disk. Alternatively, all or part of the steps of the above embodiments may be implemented by using one or more integrated circuits. Accordingly, the module units in the above embodiments may be implemented in a hardware form, or may be implemented in a form of software functional modules, and the present application is not limited to any specific form of combination of software and hardware. User equipment, terminal and UE in this application include but not limited to unmanned aerial vehicle, communication module on the unmanned aerial vehicle, remote control plane, the aircraft, small aircraft, the cell-phone, the panel computer, the notebook, vehicle-mounted Communication equipment, wireless sensor, network card, thing networking terminal, the RFID terminal, NB-IOT terminal, machine Type Communication (MTC) terminal, eMTC (enhanced MTC) terminal, the data card, network card, vehicle-mounted Communication equipment, low-cost cell-phone, wireless Communication equipment such as low-cost panel computer. The base station or the system device in the present application includes, but is not limited to, a macro cell base station, a micro cell base station, a home base station, a relay base station, a gNB (NR node B) NR node B, a TRP (Transmitter Receiver Point), and other wireless communication devices.

The above description is only a preferred embodiment of the present application, and is not intended to limit the scope of the present application. Any modification, equivalent replacement, improvement and the like made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A first node configured for wireless communication, comprising:

2. The first node of claim 1, wherein the first status report belongs to the first MAC subheader.

3. The first node of claim 1, wherein the first MAC sub-PDU comprises a second MAC payload, the second MAC payload comprising the first status report.

4. The first node of any of claims 1-3, wherein a second field is included in the first MAC subheader, the second field indicating a length of the first MAC payload.

5. The first node according to any of claims 1 to 4, comprising:

the first transmitter transmits a first message; recovering at least a first DRB along with the first message; triggering the first status report in response to a first set of conditions being met;

wherein the first message is used for a first RRC recovery procedure; the first set of conditions includes that the first RRC recovery procedure is being performed and a first data block is in effect, the first data block being associated with the first DRB; the first status report indicates a cache coherency state.

6. The first node according to any of claims 1 to 5, comprising:

a first receiver to receive first signaling used to determine whether the first field is used to indicate whether the first MAC sub-PDU includes a first status report.

7. A second node configured for wireless communication, comprising:

wherein the first MAC PDU is constructed; the first field is a field of the first MAC subheader other than the LCID field; the first MAC payload is not the first status report.

8. A method in a first node used for wireless communication, comprising:

establishing a first MAC PDU; transmitting the first MAC PDU; the first MAC PDU comprises a first MAC sub-PDU comprising a first MAC sub-header comprising at least a first field and an LCID field therein, the first field in the first MAC sub-header being used to indicate whether the first MAC sub-PDU comprises a first status report, the LCID field of the first MAC sub-PDU being used to indicate a first MAC payload;

wherein the first domain is one of the first MAC subheader other than the LCID domain; the first MAC load is not the first status report.

9. A method in a second node used for wireless communication, comprising: