A method and device used in a communication node for wireless communication
By introducing a new field and redefining the value of an existing field in the MAC subheader, the resource waste caused by the fixed length of the L field in small data transmission is solved, improving resource utilization efficiency and signaling efficiency, and reducing the probability of transmission failure.
Patent Information
- Application Number
- CN202110422003.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-04-20
- Publication Date
- 2024-11-15
- Estimated Expiration
- 2041-04-20
AI Technical Summary
In small data transmission scenarios, the length of the L field of a MAC PDU is often equal to 1 byte, causing the F field to lose its practical meaning of indicating the length, which affects resource utilization efficiency and signaling overhead.
By introducing new fields in the MAC subheader to indicate whether the MAC subPDU contains a status report, the values of existing fields are redefined to reduce the number of MAC subheaders and improve resource utilization efficiency.
The number of MAC subheaders is reduced, which avoids the failure of BSR to be triggered in a timely manner and the waste of resources, improves resource utilization efficiency, and reduces the probability of SDT transmission failure.
Smart Images

Figure CN115225223B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to a transmission method and device in a wireless communication system, and in particular to a transmission method and device for a MAC PDU. Background Art
[0002] A MAC (Medium Access Control) PDU (Protocol Data Unit) includes at least one MAC sub-PDU (subPDU), and a MAC sub-PDU includes a MAC subheader (subheader). When the MAC sub-PDU carries a MAC SDU (Service Data Unit) or a variable-length MAC CE (Control Element), the MAC subheader needs to include a length (Length, L) field (Field) to indicate the length of the MAC SDU or variable-length MAC CE carried in the MAC sub-PDU, and a format (Format, F) field is used to indicate that the length of the L field is equal to 1 byte (byte) or 2 bytes. Summary of the invention
[0003] In certain scenarios, if the amount of data transmitted is small, the length of the L field may always be equal to 1 byte or have a high probability of being equal to 1 byte, such as in SDT (Small Data Transmission) or NB-IoT (NarrowBand Internet of Things) systems. If the F field is still used to indicate the length of the L field, it will always or have a high probability of being set to 0, causing the F field to lose its practical meaning. Therefore, the format of the MAC sub-PDU needs to be enhanced.
[0004] In view of the above problems, this application provides a solution. In the description of the above problems, the NR scenario is used as an example; this application is also applicable to scenarios such as LTE (Long Term Evolution) or NB-IoT or V2X (Vehicle-to-Everything), achieving similar technical effects in the NR scenario. In addition, the use of a unified solution for different scenarios can also help reduce hardware complexity and cost.
[0005] As an embodiment, the interpretation of the terminology in the present application refers to the definition of the 3GPP specification protocol TS36 series.
[0006] As an example, the interpretation of the terms in the present application refers to the definition of the TS38 series of specification protocols of 3GPP.
[0007] As an example, the interpretation of the terms in the present application refers to the definition of the TS37 series of specification protocols of 3GPP.
[0008] As an embodiment, the interpretation of the terms in this application refers to the definition of the standard protocol of IEEE (Institute of Electrical and Electronics Engineers).
[0009] It should be noted that, in the absence of conflict, the embodiments and features in any node of the present application can be applied to any other node. In the absence of conflict, the embodiments and features in the embodiments of the present application can be arbitrarily combined with each other.
[0010] The present application discloses a method in a first node used for wireless communication, characterized by comprising:
[0011] Building a first MAC PDU; sending the first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID (Logical Channel ID) field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load;
[0012] The first field is a field in the first MAC subheader except the LCID field; and the first MAC payload is not the first status report.
[0013] As an embodiment, the problem to be solved by the present application includes: how to reduce signaling overhead.
[0014] As an embodiment, the problem to be solved by the present application includes: how to reuse the existing fields in the MAC subheader.
[0015] As an embodiment, the problem to be solved by the present application includes: how to improve resource utilization efficiency.
[0016] It is possible that the length of the L field is always equal to 1 byte or is likely to be equal to 1 byte, such as in SDT or NB-IoT systems. If the F field is still used to indicate the length of the L field, it will always be or is likely to be set to 0, causing the F field to lose its practical meaning.
[0017] As an embodiment, the characteristics of the above method include: redefining the value of the existing domain.
[0018] As an embodiment, the characteristics of the above method include: designing a new MAC subheader.
[0019] 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 sub-PDU includes a first status report, and the first field is a field in the first MAC subheader other than the LCID field; the first MAC payload is not the first status report.
[0020] As an embodiment, the characteristics of the above method include: a field other than the LCID field in the MAC subheader indicates whether there is a first status report in the MAC PDU.
[0021] 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.
[0022] As an embodiment, the characteristics of the above method include: the first MAC subheader only includes the first field and the LCID field.
[0023] As an embodiment, the characteristics of the above method include: the first MAC subheader consists of a first field and an LCID field.
[0024] As an embodiment, the benefits of the above method include: reducing one MAC subheader in the MAC PDU.
[0025] As an embodiment, the benefits of the above method include: reusing existing domains and avoiding increasing overhead.
[0026] According to one aspect of the present application, it is characterized in that the first status report belongs to the first MAC subheader.
[0027] As an embodiment, the characteristics of the above method include: a field other than the LCID field in the MAC subheader indicates whether there is a first status report in the MAC subheader.
[0028] According to one aspect of the present application, it is characterized in that the first MAC sub-PDU includes a second MAC payload, and the second MAC payload includes the first status report.
[0029] As an embodiment, the characteristics of the above method include: a field other than the LCID field in the MAC subheader indicates whether the first status report exists in the second MAC payload.
[0030] According to one aspect of the present application, it is characterized in that the first MAC subheader includes a second field, and the second field indicates the length of the first MAC payload.
[0031] As an embodiment, the characteristics of the above method include: the first MAC subheader includes a first field, an LCID field and a second field.
[0032] As an embodiment, the characteristics of the above method include: the first MAC subheader is composed of a first field, an LCID field and a second field.
[0033] As an embodiment, the characteristics of the above method include: the first MAC subheader is composed of a first field, an LCID field, a second field and a reserved field.
[0034] 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.
[0035] As an embodiment, the characteristics of the above method include: the first MAC subheader is composed of a first field, an LCID field, an eLCID field and a second field.
[0036] As an embodiment, the characteristics of the above method include: the first MAC subheader is composed of a first field, an LCID field, an eLCID field, a second field and a reserved field.
[0037] According to one aspect of the present application, it is characterized by comprising:
[0038] Sending a first message; restoring at least a first DRB (Data Radio Bearer) along with the first message; triggering the first status report in response to the first set of conditions being met;
[0039] Among them, the first message is used for the first RRC (Radio Resource Control) recovery process; the first condition set includes that the first RRC recovery process is being executed, and the first data block is effective, and the first data block is associated with the first DRB; the first status report indicates the cache-related status.
[0040] As an embodiment, the characteristics of the above method include: the first status report is for the first RRC recovery process.
[0041] According to one aspect of the present application, it is characterized by comprising:
[0042] First signaling is received, where 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.
[0043] The present application discloses a method used in a second node of wireless communication, characterized by comprising:
[0044] Receive a first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load;
[0045] Among them, the first MAC PDU is constructed; the first field is a field in the first MAC subheader except the LCID field; the first MAC payload is not the first status report.
[0046] According to one aspect of the present application, it is characterized in that the first status report belongs to the first MAC subheader.
[0047] According to one aspect of the present application, it is characterized in that the first MAC sub-PDU includes a second MAC payload, and the second MAC payload includes the first status report.
[0048] According to one aspect of the present application, it is characterized in that the first MAC subheader includes a second field, and the second field indicates the length of the first MAC payload.
[0049] According to one aspect of the present application, it is characterized by comprising:
[0050] receiving a first message;
[0051] Among them, along with the first message, at least the first DRB is restored; as a response to the first condition set being met, the first status report is triggered; the first message is used for the first RRC recovery process; the first condition set includes that the first RRC recovery process is being executed, and the first data block is effective, and the first data block is associated with the first DRB; the first status report indicates the cache-related status.
[0052] According to one aspect of the present application, it is characterized by comprising:
[0053] A first signaling is sent, wherein 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.
[0054] The present application discloses a first node used for wireless communication, characterized in that it includes:
[0055] A first transmitter is configured to construct a first MAC PDU; and transmit the first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load;
[0056] The first field is a field in the first MAC subheader except the LCID field; and the first MAC payload is not the first status report.
[0057] The present application discloses a second node used for wireless communication, characterized in that it includes:
[0058] A second receiver receives a first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load;
[0059] Among them, the first MAC PDU is constructed; the first field is a field in the first MAC subheader except the LCID field; the first MAC payload is not the first status report.
[0060] As an embodiment, compared with the traditional solution, this application has the following advantages:
[0061] -. Reduce one MAC subheader in the MAC PDU;
[0062] -. Reuse existing domains to avoid adding overhead;
[0063] -. Avoid the situation where the arrival of new data fails to trigger the BSR (Buffer Status Report) in time;
[0064] -. Avoid the situation where the uplink resources cannot accommodate a BSR and its MAC subheader and the BSR is deleted;
[0065] -. Improve resource utilization efficiency;
[0066] -. Reduce the probability of SDT transmission failure due to a timer expiration during the SDT process. BRIEF DESCRIPTION OF THE DRAWINGS
[0067] Other features, objects and advantages of the present application will become more apparent by reading the detailed description of non-limiting embodiments with reference to the following drawings:
[0068] Figure 1 A flow chart showing transmission of a first MAC PDU according to an embodiment of the present application is shown;
[0069] Figure 2 A schematic diagram of a network architecture according to an embodiment of the present application is shown;
[0070] Figure 3 A schematic diagram showing an embodiment of a wireless protocol architecture of a user plane and a control plane according to an embodiment of the present application;
[0071] Figure 4 A schematic diagram showing a first communication device and a second communication device according to an embodiment of the present application is shown;
[0072] Figure 5 A flow chart showing wireless signal transmission according to an embodiment of the present application is shown;
[0073] Figure 6 A flowchart of wireless signal transmission according to another embodiment of the present application is shown;
[0074] Figure 7 A schematic diagram showing that a first status report belongs to a first MAC subheader according to an embodiment of the present application;
[0075] Figure 8 A schematic diagram showing that a second MAC payload includes a first status report according to an embodiment of the present application;
[0076] Fig. 9 A schematic diagram showing the format of a first MAC sub-PDU according to an embodiment of the present application;
[0077] Fig.10 A schematic diagram showing the format of a first MAC sub-PDU according to another embodiment of the present application;
[0078] Fig.11 A schematic diagram showing the format of a first MAC sub-PDU according to yet another embodiment of the present application;
[0079] Fig.12 A schematic diagram of a first MAC subheader according to a first embodiment of the present application is shown;
[0080] Fig.13 A schematic diagram of a first MAC subheader according to a second embodiment of the present application is shown;
[0081] Fig.14 A schematic diagram of a first MAC subheader according to a third embodiment of the present application is shown;
[0082] Fig.15 A schematic diagram of a first MAC subheader according to a fourth embodiment of the present application is shown;
[0083] Fig.16 A schematic diagram of a first MAC subheader according to a fifth embodiment of the present application is shown;
[0084] Fig.17 A schematic diagram of a first MAC subheader according to a sixth embodiment of the present application is shown;
[0085] Fig.18 A schematic diagram of a first MAC subheader according to a seventh embodiment of the present application is shown;
[0086] Fig.19 A schematic diagram of a first MAC subheader according to an eighth embodiment of the present application is shown;
[0087] Fig. 20 A schematic diagram showing a first MAC load and a second MAC load according to an embodiment of the present application is shown;
[0088] Fig.21 A schematic diagram showing a first MAC load and a second MAC load according to another embodiment of the present application is shown;
[0089] Fig. 22 A structural block diagram of a processing device used in a first node according to an embodiment of the present application is shown;
[0090] Fig.23 A structural block diagram of a processing device used in a second node according to an embodiment of the present application is shown;
[0091] Fig.24 A schematic diagram of a target domain or a second MAC load domain according to an embodiment of the present application is shown. DETAILED DESCRIPTION
[0092] The technical solution of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be noted that, unless there is a conflict, the embodiments in the present application and the features in the embodiments can be combined with each other arbitrarily.
[0093] Example 1
[0094] Embodiment 1 illustrates a flow chart of the transmission of the first MAC PDU according to an embodiment of the present application, as shown in the attached Figure 1 Attached Figure 1 In the figure, each box represents a step. It should be emphasized that the order of the boxes in the figure does not represent the temporal relationship between the steps represented.
[0095] In Example 1, the first node in the present application, in step 101, constructs a first MAC PDU; sends the first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load; wherein the first field is a field in the first MAC sub-header other than the LCID field; the first MAC load is not the first status report.
[0096] As an embodiment, a MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a field including a parameter means that: the field indicates the parameter.
[0097] As an embodiment, a MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a field including a parameter means that the MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a field displays and indicates the parameter.
[0098] As an embodiment, a MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a field including a parameter means that the MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a field implicitly indicates the parameter.
[0099] As an embodiment, a MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a field including a parameter means that the MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a field is used to determine the parameter.
[0100] As an embodiment, a MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a domain includes a parameter, which means that the parameter is included in the MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a domain.
[0101] As an embodiment, a MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a domain includes a parameter, which means that the MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a domain carries the parameter.
[0102] As an embodiment, a MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a domain includes a parameter, which means that the MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC payload or a domain includes another domain, and the other domain includes the parameter.
[0103] As an embodiment, the first MAC PDU is a protocol data unit (Protocol Data Unit) of the MAC layer.
[0104] As an embodiment, the first MAC PDU is a MAC PDU.
[0105] As a sub-embodiment of this embodiment, the MAC PDU is a bit string that is byte aligned in length (eg, multiple 8 bits).
[0106] As a sub-embodiment of this embodiment, the leftmost bit of the first line in the bit string is the highest bit (the most significant bit is the leftmost bit of the first line of the table), and the rightmost bit of the last line in the bit string is the lowest bit (the least significant bit is the rightmost bit on the last line of the table).
[0107] As a sub-embodiment of this embodiment, the bit string is to be read from left to right and in the reading order of the lines.
[0108] As an embodiment, the behavior of forming the first MAC PDU includes: multiplexing of MAC CE and MAC SDU.
[0109] As an embodiment, the behavior of forming the first MAC PDU includes: logical channel prioritization (Logical Channel Prioritization, LCP).
[0110] As an embodiment, the behavior of forming the first MAC PDU includes: selection of logical channels.
[0111] As an embodiment, the behavior of forming the first MAC PDU includes: resource allocation (ResourceAllocation).
[0112] As an embodiment, the behavior of forming the first MAC PDU includes: connecting multiple MAC sub-PDUs in series according to the format of the MAC PDU.
[0113] As an embodiment, the behavior of forming the first MAC PDU includes: obtaining the first MAC PDU.
[0114] As an embodiment, the first MAC PDU is sent via an air interface.
[0115] As a sub-embodiment of this embodiment, the air interface includes an interface between two UEs.
[0116] As a sub-embodiment of this embodiment, the air interface includes an interface between two gNBs / eNGs.
[0117] As a sub-embodiment of this embodiment, the air interface includes an interface between two gNBs / eNGs.
[0118] As a sub-embodiment of this embodiment, the air interface includes an interface between a UE and a gNB / eNB.
[0119] As a sub-embodiment of this embodiment, the air interface includes an interface between the first node and the second node.
[0120] As an embodiment, the phrase "the first MAC PDU includes 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 is the one MAC sub-PDU or the first MAC sub-PDU is one MAC sub-PDU among the more MAC sub-PDUs.
[0121] As an embodiment, the phrase that the first MAC PDU includes a first MAC sub-PDU includes: the first MAC PDU includes a MAC sub-PDU, and the first MAC sub-PDU is the one MAC sub-PDU.
[0122] As a sub-embodiment of this embodiment, the first MAC sub-PDU includes only one MAC sub-header.
[0123] As a sub-embodiment of this embodiment, the first MAC sub-PDU includes a MAC sub-header and a MAC SDU.
[0124] As a sub-embodiment of this embodiment, the first MAC sub-PDU includes a MAC sub-header and a MACCE.
[0125] As a sub-embodiment of this embodiment, the first MAC sub-PDU includes a MAC sub-header and padding.
[0126] As an embodiment, the phrase "the first MAC PDU includes a first MAC sub-PDU" includes: the first MAC PDU includes more MAC sub-PDUs, the more MAC sub-PDUs include at least 2 MAC sub-PDUs, and the first MAC sub-PDU is one MAC sub-PDU among the more MAC sub-PDUs.
[0127] As a sub-embodiment of this embodiment, the first MAC sub-PDU consists of only one MAC sub-header.
[0128] As a sub-embodiment of this embodiment, the first MAC sub-PDU consists of a MAC sub-header and a MAC SDU.
[0129] As a sub-embodiment of this embodiment, the first MAC sub-PDU consists of a MAC sub-header and a MAC CE.
[0130] As a sub-embodiment of this embodiment, the first MAC sub-PDU consists of a MAC sub-header and padding.
[0131] As a sub-embodiment of this embodiment, a MAC sub-PDU other than the first MAC sub-PDU among the more MAC sub-PDUs consists of only one MAC sub-header.
[0132] As a sub-embodiment of this embodiment, a MAC sub-PDU among the more MAC sub-PDUs except the first MAC sub-PDU consists of a MAC sub-header and a MAC SDU.
[0133] As a sub-embodiment of this embodiment, a MAC sub-PDU other than the first MAC sub-PDU among the more MAC sub-PDUs consists of a MAC sub-header and a MAC CE.
[0134] As a sub-embodiment of this embodiment, a MAC sub-PDU among the more MAC sub-PDUs except the first MAC sub-PDU consists of a MAC sub-header and padding.
[0135] As an embodiment, the first MAC sub-PDU is the first MAC sub-PDU in the first MAC PDU.
[0136] As an embodiment, the first MAC sub-PDU is any MAC sub-PDU in the first MAC PDU.
[0137] As an embodiment, the first MAC PDU is composed of the first MAC sub-PDU.
[0138] As an embodiment, the phrase that the first MAC sub-PDU includes a first MAC sub-header includes: the first MAC sub-header is a MAC sub-header for the first MAC sub-PDU.
[0139] As an embodiment, the phrase that the first MAC sub-PDU includes a first MAC sub-header includes: the first MAC sub-header is a MAC sub-header in the first MAC sub-PDU.
[0140] As an embodiment, the phrase that the first MAC sub-PDU includes a first MAC sub-header includes: the first MAC sub-header belongs to the first MAC sub-PDU.
[0141] As an embodiment, the phrase that the first MAC sub-PDU includes a first MAC sub-header includes: the first MAC sub-header indicates the first MAC sub-PDU.
[0142] As an embodiment, the phrase that the first MAC sub-PDU includes a first MAC sub-header includes: the first MAC sub-header is used to determine the first MAC sub-PDU.
[0143] 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.
[0144] As an embodiment, the first MAC sub-PDU includes only one MAC sub-header, and the one MAC sub-header is the first MAC sub-header.
[0145] As an embodiment, the first MAC sub-header includes a MAC sub-header.
[0146] As an embodiment, the first MAC subheader is a bit string that is byte aligned in length (eg, multiple 8 bits).
[0147] As an embodiment, the first MAC subheader is placed immediately in front of the corresponding MACSDU, MAC CE, or padding.
[0148] As an embodiment, the first MAC subheader is composed of an R (Reserved) field, an F (Format) field, an LCID field and an L (Length) field; wherein a MAC sub-PDU to which the MAC subheader belongs is not a MAC CE of a fixed size, or is filled with or includes one of the MAC SDUs of the UL CCCH (Common Control Channel).
[0149] As an embodiment, the first MAC subheader is composed of an R field, an F field, an LCID field, an eLCID field and an L field; wherein, a MAC sub-PDU to which the MAC subheader belongs is not a MAC CE of a fixed size, or one of the MAC SDUs that fill or include UL CCCH.
[0150] As an embodiment, the first MAC subheader is composed of an R field and an LCID field; wherein, a MAC sub-PDU to which the MAC subheader belongs includes a MAC CE of a fixed size, or fills or includes a MAC SDU of UL (UpLink) CCCH.
[0151] As an embodiment, the first MAC subheader is composed of an R field, an LCID field and an eLCID field; wherein a MAC sub-PDU to which the MAC subheader belongs includes a MAC CE of a fixed size, or a MAC SDU filled with or including a UL CCCH.
[0152] As an embodiment, the phrase that the first MAC subheader includes at least a first field and an LCID field includes: the first field and the LCID field are two fields in the first MAC subheader.
[0153] As an embodiment, the phrase that the first MAC subheader includes at least the first field and the LCID field includes: the first MAC subheader only includes the first field and the LCID field.
[0154] As a sub-embodiment of this embodiment, the first MAC subheader consists of the first field and the LCID field.
[0155] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is placed directly before the LCID field.
[0156] As an embodiment, the phrase that the first MAC subheader includes at least the first field and the LCID field includes: in addition to the first field and the LCID field, the first MAC subheader also includes other fields.
[0157] As an embodiment, the phrase "the first MAC subheader includes at least a first domain and an LCID domain" includes: the first MAC subheader includes at least 3 MAC domains, and the first domain and the LCID domain are two domains of the at least 3 MAC domains.
[0158] As a sub-embodiment of this embodiment, the first MAC sub-header includes 3 MAC fields.
[0159] As a sub-embodiment of this embodiment, the first MAC sub-header includes 4 MAC fields.
[0160] As a sub-embodiment of this embodiment, the first MAC sub-header includes 5 MAC fields.
[0161] As a sub-embodiment of this embodiment, the first MAC sub-header includes 6 MAC fields.
[0162] As an embodiment, the phrase, the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report, including: the first field in the first MAC subheader indicates whether the first MAC sub-PDU includes a first status report.
[0163] As an embodiment, the phrase, the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report, including: the first field in the first MAC subheader is used to determine whether the first MAC sub-PDU includes a first status report.
[0164] As an embodiment, the phrase, the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report including: the first field in the first MAC subheader indicates whether there is a byte in the first MAC sub-PDU including the first status report.
[0165] As an embodiment, the phrase, the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report, including: the first field in the first MAC subheader indicates that the first MAC sub-PDU includes the first status report.
[0166] As an embodiment, the phrase that the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report includes: the first field in the first MAC subheader indicates that the first MAC sub-PDU does not include the first status report.
[0167] As an embodiment, the phrase, the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report, including: the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a field, and the field includes the first status report.
[0168] As an embodiment, the phrase, the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report, including: the first MAC sub-PDU includes a field, and the field is used to indicate the first status report; the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes the first status report.
[0169] As a sub-embodiment of this embodiment, the one field is set to a default value to indicate that the first status report is not included in the first MAC sub-PDU.
[0170] As a sub-embodiment of this embodiment, the one field is set to a specific value to indicate that the first status report is included in the first MAC sub-PDU.
[0171] As an embodiment, the phrase, the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report including: the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes the first status report field in the present application, and the first status report field includes a first status report.
[0172] As an embodiment, the first field in the first MAC subheader indicates that the first MAC sub-PDU includes the first status report which is used to determine that the first node has at least one more uplink transmission.
[0173] As an embodiment, the first field in the first MAC subheader indicates that the first MAC sub-PDU does not include the first status report used to determine that the first node has no expected uplink transmission.
[0174] As an embodiment, only the first MAC sub-PDU in the first MAC PDU is used to indicate whether the first MAC sub-PDU includes a field for a first status report.
[0175] As a sub-embodiment of this embodiment, a field used to indicate whether the first MAC sub-PDU includes a first status report does not exist in the MAC subheader of other MAC sub-PDUs in the first MAC PDU except the first MAC sub-PDU.
[0176] As a sub-embodiment of this embodiment, the first MAC sub-PDU is any MAC sub-PDU in the first MAC PDU.
[0177] As a sub-embodiment of this embodiment, the first MAC sub-PDU is the first MAC sub-PDU in the first MAC PDU.
[0178] As a sub-embodiment of this embodiment, the first status report is only for the logical channel corresponding to the LCID field in the first MAC sub-PDU.
[0179] As a sub-embodiment of this embodiment, the first status report is for the logical channel group (Logical Channel Group, LCG) to which the logical channel corresponding to the LCID field in the first MAC sub-PDU belongs.
[0180] As an embodiment, the first field in the MAC subheader of each MAC sub-PDU in the first MAC PDU is used to indicate whether the first MAC sub-PDU includes a first status report.
[0181] As a sub-embodiment of this embodiment, the first MAC sub-PDU is any MAC sub-PDU in the first MAC PDU.
[0182] As a sub-embodiment of this embodiment, the first status report is only for the logical channel corresponding to the LCID field in the first MAC sub-PDU.
[0183] As an embodiment, the first status report indication is used to provide the uplink data volume (UL data volume) of the MAC entity.
[0184] As a sub-embodiment of this embodiment, the uplink data amount is the sum of valid data when the first MAC PDU is sent for the first time after being constructed.
[0185] As a sub-embodiment of this embodiment, the uplink data amount is the sum of valid data when the first MAC PDU is resent.
[0186] As a sub-embodiment of this embodiment, when the first MAC PDU is resent, the first status report is updated.
[0187] As a sub-embodiment of this embodiment, when the first MAC PDU is resent, the first status report is not updated.
[0188] As a sub-embodiment of this embodiment, the uplink data volume does not count the size of the RLC (Radio Link Control, wireless link layer control protocol) header and the MAC subheader.
[0189] As a sub-embodiment of this embodiment, the uplink data amount calculates the size of the RLC header and the MAC subheader.
[0190] As a sub-embodiment of this embodiment, the uplink data volume is the data volume on the logical channel indicated by the LCID field in the first MAC subheader.
[0191] As a sub-embodiment of this embodiment, the uplink data volume is the data volume on a logical channel group to which the logical channel indicated by the LCID field in the first MAC subheader belongs.
[0192] As an embodiment, the first status report is used in the SDT process.
[0193] As an embodiment, the first status report includes a BSR.
[0194] As an embodiment, the first status report includes an Inactive BSR.
[0195] As an embodiment, the first status report includes IBSR (Inactive BSR).
[0196] As an embodiment, the first status report includes an IDT BSR.
[0197] As an embodiment, the first status report includes an SDT BSR.
[0198] As an embodiment, the first status report includes a DVR (Data Volume Report).
[0199] As an embodiment, the first status report includes a DSR (Data Buffer Report).
[0200] As an embodiment, the first status report includes a PHR (Power Headroom Report).
[0201] As an embodiment, the first status report includes a BFR (Beam Failure Report).
[0202] As an embodiment, the first status report includes Listen Before Talk failure (LBT failure).
[0203] As an embodiment, the first status report includes release assistant information (RAI), and the release assistant information is used to indicate whether the first node still has expected uplink or downlink transmission.
[0204] As an embodiment, the first domain includes an F domain.
[0205] As an embodiment, the first domain includes an R domain.
[0206] As an embodiment, the first domain includes an F domain and an R domain.
[0207] As an embodiment, the first domain includes a RAI domain.
[0208] As an embodiment, the size of the first field is 1 bit.
[0209] As an embodiment, the size of the first field is 2 bits.
[0210] As an embodiment, the size of the first field is 3 bits.
[0211] As an embodiment, the first domain is set to one of a first target value or a second target value.
[0212] As a sub-embodiment of this embodiment, the length of the first field is equal to 1 bit.
[0213] As a sub-embodiment of this embodiment, the length of the first field is equal to 2 bits.
[0214] As a sub-embodiment of this embodiment, the first target value and the second target value are not equal.
[0215] As a sub-embodiment of this embodiment, the first target value is equal to 1, and the second target value is equal to 0.
[0216] As a sub-embodiment of this embodiment, the first target value is equal to 0, and the second target value is equal to 1.
[0217] As a sub-embodiment of this embodiment, the first target value is equal to a value among 00, 01, 10, 11, and the second target value is equal to another value among 11, 10, 10, 00.
[0218] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to the first target value to indicate that the first MAC sub-PDU includes a first status report; the first field in the first MAC subheader is set to the second target value to indicate that the first MAC sub-PDU does not include a first status report.
[0219] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to the first target value to indicate that the first MAC sub-PDU includes the second field and the first MAC subheader includes a first status report; the first field in the first MAC sub-PDU is set to the second target value to indicate that the first MAC sub-PDU includes an L field and the first MAC sub-PDU does not include a first status report; wherein the length of the one L field is equal to 1 byte.
[0220] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value which is reserved and is not used to indicate any information, and the given value is a value among 00, 01, 10, 11 except the first target value and the second target value.
[0221] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to the first target value to indicate that the target domain in the present application exists; the first field in the first MAC subheader is set to the second target value to indicate that the target domain in the present application does not exist.
[0222] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to the first target value to indicate that the first status reporting field in the present application exists; the first field in the first MAC subheader is set to the second target value to indicate that the first status reporting field in the present application does not exist.
[0223] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to the first target value to indicate that the second MAC load field in the present application exists; the first field in the first MAC subheader is set to the second target value to indicate that the second MAC load field in the present application does not exist.
[0224] As an embodiment, the first domain is set to one of a first given value, a second given value, a third given value or a fourth given value.
[0225] As a sub-embodiment of this embodiment, the length of the first field is equal to 2 bits.
[0226] As a sub-embodiment of this embodiment, the first given value is equal to 00, the second given value is equal to 01, the first given value is equal to 10, and the second given value is equal to 11.
[0227] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report and release assistance information.
[0228] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value to indicate that the first MAC sub-PDU includes a first status report; wherein the given value is one of the first given value, the second given value, the third given value or the fourth given value.
[0229] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value to indicate that the first MAC sub-PDU does not include a first status report, and the given value is one of the first given value, the second given value, the third given value or the fourth given value.
[0230] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value to indicate that no auxiliary information is released; wherein the given value is one of the first given value, the second given value, the third given value or the fourth given value.
[0231] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value to indicate that there is release auxiliary information; wherein, the release auxiliary information indicates that no subsequent downlink and uplink data transmission is expected, and the one given value is one of the first given value, the second given value, the third given value or the fourth given value.
[0232] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value to indicate that there is release assistance information; wherein, the release assistance information indicates that a subsequent downlink transmission is expected, and the given value is one of the first given value, the second given value, the third given value or the fourth given value.
[0233] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value to indicate that the first MAC sub-PDU includes a first status report and no auxiliary information is released; wherein the given value is one of the first given value, the second given value, the third given value or the fourth given value.
[0234] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value to indicate that the first MAC sub-PDU does not include a first status report and has release auxiliary information; wherein the release auxiliary information indicates that no subsequent downlink and uplink data transmission is expected, and the one given value is one of the first given value, the second given value, the third given value or the fourth given value.
[0235] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value to indicate that the first MAC sub-PDU does not include a first status report and that there is release assistance information; wherein the release assistance information indicates that a subsequent downlink transmission is expected, and the one given value is one of the first given value, the second given value, the third given value or the fourth given value.
[0236] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value to indicate that the first MAC sub-PDU does not include a first status report and no auxiliary information is released; wherein the given value is one of the first given value, the second given value, the third given value or the fourth given value.
[0237] As a sub-embodiment of this embodiment, the first field in the first MAC subheader is set to a given value and is reserved and is not used to indicate any information.
[0238] As a sub-embodiment of this embodiment, any two of the first given value, the second given value, the third given value and the fourth given value are not equal.
[0239] As an embodiment, the first MAC load includes a MAC CE.
[0240] As a sub-embodiment of this embodiment, the MAC CE is a bit string that is byte aligned in length (eg, multiple 8 bits).
[0241] As an embodiment, the first MAC payload includes a MAC SDU.
[0242] As a sub-embodiment of this embodiment, the MAC SDU is a bit string that is byte aligned in length (eg, multiple 8 bits).
[0243] As a sub-embodiment of this embodiment, the one MAC SDU is included into a MAC PDU from the first bit onward.
[0244] As an embodiment, the first MAC payload includes 0 bits.
[0245] As an embodiment, the first MAC payload includes at least 1 bit.
[0246] As an embodiment, the first MAC payload includes at least 1 byte.
[0247] As an embodiment, the phrase the LCID field of the first MAC sub-PDU is used to indicate that the first MAC load includes: the LCID field of the first MAC sub-PDU is set to the code point / index of the LCID corresponding to the first MAC load.
[0248] As an embodiment, the phrase: the LCID field of the first MAC sub-PDU is used to indicate that the first MAC payload includes: the LCID field of the first MAC sub-PDU indicates that the first MAC payload is included in the first MAC sub-PDU.
[0249] As an embodiment, the phrase that the LCID field of the first MAC sub-PDU is used to indicate the first MAC load includes: the first MAC load in the first MAC sub-PDU is indicated by the LCID field in the first MAC sub-PDU.
[0250] As an embodiment, the phrase "the LCID field of the first MAC sub-PDU" is used to indicate that the first MAC load includes: the LCID field of the first MAC sub-PDU is used to indicate that the first MAC sub-PDU includes the first MAC load field in the present application, and the first MAC load field includes the first MAC load.
[0251] As an embodiment, the phrase the LCID field of the first MAC sub-PDU is used to indicate that the first MAC payload includes: the LCID field of the first MAC sub-PDU is associated with the first MAC payload.
[0252] As an embodiment, the first MAC sub-PDU includes the first MAC payload.
[0253] As an embodiment, the first MAC subheader is placed directly before the first MAC payload.
[0254] As an embodiment, the first MAC subheader is placed directly before the second MAC payload.
[0255] As an embodiment, the first MAC payload is associated with a LCID.
[0256] As an embodiment, the first MAC payload corresponds to an LCID.
[0257] As an embodiment, the first MAC payload includes CCCH SDU.
[0258] As an embodiment, the first MAC payload includes a DTCH SDU.
[0259] As an embodiment, the first MAC payload includes a DCCH SDU.
[0260] As an embodiment, the first MAC payload includes a MAC SDU.
[0261] As an embodiment, the first MAC load includes MAC CE.
[0262] As an embodiment, the phrase that the first field is a field in the first MAC subheader other than the LCID field includes: the first field belongs to the first MAC subheader, and the first field is not the LCID field.
[0263] As an embodiment, the phrase that the first field is a field other than the LCID field in the first MAC subheader includes: the first field is the R field in Section 6.1.2 of 3GPP TS 38.321.
[0264] As an embodiment, the phrase that the first field is a field other than the LCID field in the first MAC subheader includes: the first field is the F field of Section 6.1.2 in 3GPP TS 38.321.
[0265] As an embodiment, the phrase that the first field is a field other than the LCID field in the first MAC subheader includes: the first field is the L field in Section 6.1.2 of 3GPP TS 38.321.
[0266] As an embodiment, the phrase that the first field is a field other than the LCID field in the first MAC subheader includes: the first field is the entire L field of Section 6.1.2 in 3GPP TS 38.321.
[0267] As an embodiment, the phrase that the first field is a field other than the LCID field in the first MAC subheader includes: the first field is part of the L field in Section 6.1.2 of 3GPP TS 38.321.
[0268] As an embodiment, the phrase that the first field is a field other than the LCID field in the first MAC subheader includes: the first field is the R field in Section 6.1.2 of 3GPP TS 38.321, or at least one of the F field or the L field.
[0269] As an embodiment, the phrase that the first field is a field other than the LCID field in the first MAC subheader includes: the first field is the R field in Section 6.1.2 of 3GPP TS 38.321, or at least one of the F fields.
[0270] As an embodiment, the phrase that the first field is a field other than the LCID field in the first MAC subheader includes: the first field is the R field in Section 6.1.2 of 3GPP TS 38.321, or at least one of the F fields.
[0271] As an embodiment, the phrase that the first field is a field in the first MAC subheader other than the LCID field includes: the first field is the R field in Section 6.1.2 of 3GPP TS 38.321, or at least one of all or part of the F field or the L field.
[0272] As an embodiment, the phrase that the first field is a field in the first MAC subheader other than the LCID field includes: the first field is the R field in Section 6.1.2 of 3GPP TS 38.321, or the F field, or the L field or at least one of the LCID field.
[0273] As an embodiment, the phrase "the first domain is a domain in the first MAC subheader other than the LCID domain" includes: the first domain is the R domain of Section 6.1.2 in 3GPP TS 38.321, or the F domain, or all or part of the L domain, or at least one of all or part of the LCID domain.
[0274] As an embodiment, the LCID field indicates the logical channel instance of the corresponding MAC SDU (logical channel instance of the corresponding MAC SDU) or the type of the corresponding MAC CE (the type of the corresponding MAC CE) or padding.
[0275] As an embodiment, the LCID field includes 6 bits, and the 6 bits are used to determine 64 code points (Codepoint) / indexes (Index), and one code point / index among the 64 code points / indexes indicates the type or padding of the logical channel instance of the corresponding MAC SDU or the corresponding MAC CE.
[0276] As an embodiment, the phrase "the first MAC load is not the first status report" includes: the first status report does not belong to the first MAC load.
[0277] As an embodiment, the phrase "the first MAC payload is not the first status report" includes: the first MAC payload is the first MAC SDU, and the first status report is not a MAC SDU.
[0278] As an embodiment, the phrase "the first MAC load is not the first status report" includes: the first MAC load is a MAC CE, and the first status report is not the one MAC CE.
[0279] As an embodiment, the phrase "the first MAC load is not the first status report" includes: information carried by the first MAC load and the first status report is different.
[0280] As an embodiment, the phrase "the first MAC payload is not the first status report" includes: the first status report is not included in the first MAC payload.
[0281] As an embodiment, the first status report is used for beam failure recovery (BFR) reporting.
[0282] As a sub-embodiment of this embodiment, the LCID field is not set to 50 or 51.
[0283] As a sub-embodiment of this embodiment, when the LCID field is set to 34, the eLCID field is not set to 251.
[0284] As an embodiment, the first status report is used for data volume reporting.
[0285] As a sub-embodiment of this embodiment, the LCID field is not set to 59, or 60, or 61, or 62.
[0286] As a sub-embodiment of this embodiment, the LCID field is not set to 45 or 46.
[0287] As a sub-embodiment of this embodiment, when the LCID field is set to 34, the eLCID field is not set to 255.
[0288] As an embodiment, the first status report is used for power headroom reporting (PHR).
[0289] As a sub-embodiment of this embodiment, the LCID field is not set to 54, or 56, or 57.
[0290] As a sub-embodiment of this embodiment, the LCID field is not set to 45 or 46.
[0291] As a sub-embodiment of this embodiment, when the LCID field is set to 34, the eLCID field is not set to 255.
[0292] As an embodiment, the first status report is used for reporting a listen-before-speak failure.
[0293] As a sub-embodiment of this embodiment, the LCID field is not set to 54, or 56, or 57.
[0294] As a sub-embodiment of this embodiment, the LCID field is not set to 45 or 46.
[0295] As a sub-embodiment of this embodiment, when the LCID field is set to 34, the eLCID field is not set to 255.
[0296] As an embodiment, the first status report is used to release auxiliary information.
[0297] As a sub-embodiment of this embodiment, the LCID field is set to an integer not less than 0 and not greater than 63.
[0298] As a sub-embodiment of this embodiment, the LCID field is set to an integer not less than 0 and not greater than 63.
[0299] As a sub-embodiment of this embodiment, the LCID field is equal to 33, and the eLCID field is set to be not less than 0 and not greater than 2. 16 An integer of -1.
[0300] 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 greater than 249.
[0301] As an embodiment, the definition of the eLCID domain in the present application refers to Section 6.2.1 in 3GPP TS38.321.
[0302] As an embodiment, the L domain in the present application refers to the L domain in Section 6.2.1 of 3GPP TS38.321.
[0303] As an embodiment, the F domain in the present application refers to the F domain in Section 6.2.1 of 3GPP TS38.321.
[0304] As an embodiment, the length of the R field in the present application is equal to 1 bit or 2 bits.
[0305] As an embodiment, the R field in the present application is set to 0.
[0306] As an embodiment, the first domain in the present application includes at least one of the F domain or the R domain.
[0307] As an embodiment, the first domain in the present application does not include the F domain or the R domain.
[0308] As an embodiment, the first domain in the present application is not the F domain or the R domain.
[0309] As an embodiment, the first field in the present application reuses the position of the F field or the R field in the MAC subheader.
[0310] As an embodiment, the first field in the present application is a field in a redefined MAC subheader.
[0311] As an embodiment, the target domain in the present application includes the L domain.
[0312] As an embodiment, the target domain in the present application does not include the L domain.
[0313] As an embodiment, the target domain in the present application is not the L domain.
[0314] As an embodiment, the target domain in the present application is a domain in a redefined MAC subheader.
[0315] As an embodiment, the second MAC payload domain and the first MAC payload domain in the present application use the first MAC subheader together.
[0316] Example 2
[0317] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in the attached Figure 2 Attached Figure 2A diagram of a network architecture 200 of a 5G NR (New Radio), LTE (Long-Term Evolution) and LTE-A (Long-Term Evolution Advanced) system is illustrated. The 5G NR or LTE network architecture 200 may be referred to as a 5G System (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-RAN (Next Generation Radio Access Network) 202, 5GC (5G Core Network) / EPC (Evolved Packet Core) 210, HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and Internet services 230. The 5GS / EPS may be interconnected with other access networks, but these entities / interfaces are not shown for simplicity. As shown, 5GS / EPS provides packet-switched services, however, those skilled in the art will readily appreciate that the various concepts presented throughout this application can be extended to networks providing circuit-switched services or other cellular networks. NG-RAN includes NR Node B (gNB) 203 and other gNBs 204. gNB 203 provides user and control plane protocol terminations toward UE 201. gNB 203 can be connected to other gNBs 204 via an Xn interface (e.g., backhaul). gNB 203 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 term. gNB 203 provides an access point to 5GC / EPC 210 for UE 201. Examples of UE 201 include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop computer, 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., an MP3 player), a camera, a game console, a drone, an aircraft, a narrowband Internet of Things device, a machine type communication device, a land vehicle, an automobile, a wearable device, or any other similarly functional device.A person 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 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 term. gNB203 is connected to 5GC / EPC210 via an S1 / NG interface. 5GC / EPC210 includes MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MME / AMF / SMF214, S-GW (Service Gateway) / UPF (User Plane Function) 212, and P-GW (Packet Data Network Gateway) / UPF213. MME / AMF / SMF211 is the control node that handles the signaling between UE201 and 5GC / EPC210. In general, MME / AMF / SMF211 provides bearer and connection management. All user IP (Internet Protocal) packets are transmitted through S-GW / UPF212, which itself is connected to P-GW / UPF213. P-GW provides UE IP address allocation and other functions. P-GW / UPF213 is connected to Internet services 230. Internet services 230 include operator-corresponding Internet protocol services, which may specifically include Internet, intranet, IMS (IP Multimedia Subsystem) and packet switching streaming services.
[0318] As an embodiment, the UE201 corresponds to the first node in the present application.
[0319] As an embodiment, the UE 201 is a user equipment (User Equipment, UE).
[0320] As an embodiment, the gNB203 corresponds to the second node in this application.
[0321] As an embodiment, the gNB203 is a base station device (BaseStation, BS).
[0322] As an embodiment, the gNB203 is a user equipment.
[0323] As an embodiment, the gNB203 is a relay.
[0324] As an embodiment, the gNB203 is a gateway.
[0325] As an embodiment, the user equipment supports transmission of a terrestrial network (Non-Terrestrial Network, NTN).
[0326] As an embodiment, the user equipment supports transmission of a non-terrestrial network (Terrestrial Network).
[0327] As an embodiment, the user equipment supports transmission in a network with a large delay difference.
[0328] As an embodiment, the user equipment supports dual connection (DC) transmission.
[0329] As an embodiment, the user equipment includes an aircraft.
[0330] As an embodiment, the user equipment includes a vehicle-mounted terminal.
[0331] As an embodiment, the user equipment includes a vessel.
[0332] As an embodiment, the user equipment includes an Internet of Things terminal.
[0333] As an embodiment, the user equipment includes a terminal of the industrial Internet of Things.
[0334] As an embodiment, the user equipment includes a device supporting low-latency and high-reliability transmission.
[0335] As an embodiment, the user equipment includes a test device.
[0336] As an embodiment, the user equipment includes a signaling tester.
[0337] As an embodiment, the base station device supports transmission in a non-terrestrial network.
[0338] As an embodiment, the base station device supports transmission in a network with a large delay difference.
[0339] As an embodiment, the base station device supports transmission of a terrestrial network.
[0340] As an embodiment, the base station device includes a macro cellular (Marco Cellular) base station.
[0341] As an embodiment, the base station device includes a micro cell base station.
[0342] As an embodiment, the base station device includes a pico cell (Pico Cell) base station.
[0343] As an embodiment, the base station device includes a home base station (Femtocell).
[0344] As an embodiment, the base station device includes a base station device that supports a large delay difference.
[0345] As an embodiment, the base station device includes a flying platform device.
[0346] As an embodiment, the base station device includes a satellite device.
[0347] As an embodiment, the base station device includes a TRP (Transmitter Receiver Point).
[0348] As an embodiment, the base station device includes a CU (Centralized Unit).
[0349] As an embodiment, the base station device includes a DU (Distributed Unit).
[0350] As an embodiment, the base station device includes a testing device.
[0351] As an embodiment, the base station equipment includes a signaling tester.
[0352] As an embodiment, the base station equipment includes an IAB (Integrated Access and Backhaul)-node.
[0353] As an embodiment, the base station device includes an IAB-donor.
[0354] As an embodiment, the base station device includes an IAB-donor-CU.
[0355] As an embodiment, the base station device includes an IAB-donor-DU.
[0356] As an embodiment, the base station device includes an IAB-DU.
[0357] As an embodiment, the base station device includes IAB-MT.
[0358] As an embodiment, the relay includes a relay.
[0359] As an embodiment, the relay includes an L3 relay.
[0360] As an embodiment, the relay includes an L2 relay.
[0361] As an embodiment, the relay includes a router.
[0362] As an embodiment, the relay includes a switch.
[0363] As an embodiment, the relay includes a user equipment.
[0364] As an embodiment, the relay includes a base station device.
[0365] Example 3
[0366] Embodiment 3 shows a schematic diagram of an embodiment of a wireless protocol architecture of a user plane and a control plane according to the present application, as shown in the attached Figure 3 shown. Figure 3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300, Figure 3The radio protocol architecture for the control plane 300 is shown in 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 as PHY 301 herein. Layer 2 (L2 layer) 305 is above PHY 301 and includes a MAC (Medium Access Control) sublayer 302, an RLC (Radio Link Control) 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 encrypting data packets, and provides inter-zone mobility support. The RLC sublayer 303 provides segmentation and reassembly of upper layer data packets, retransmission of lost data packets, and reordering of data 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 a 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 using RRC signaling to configure lower layers. The radio protocol architecture of the user plane 350 includes layer 1 (L1 layer) and layer 2 (L2 layer). In the user plane 350, the radio protocol architecture is substantially the same as the corresponding layers and sublayers in the control plane 300 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, but the PDCP sublayer 354 also provides header compression for upper layer data packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes a SDAP (Service Data Adaptation Protocol) sublayer 356. The SDAP sublayer 356 is responsible for mapping between QoS flows and data radio bearers (DRBs) to support service diversity.
[0367] As an example, Figure 3 The wireless protocol architecture in is applicable to the first node in this application.
[0368] As an example, Figure 3 The wireless protocol architecture in is applicable to the second node in this application.
[0369] As an embodiment, the first message in the present application is generated in the RRC306.
[0370] As an embodiment, the first message in the present application is generated by the MAC302 or MAC352.
[0371] As an embodiment, the first message in the present application is generated by the PHY301 or PHY351.
[0372] As an embodiment, the first signaling in the present application is generated in the RRC306.
[0373] As an embodiment, the first signaling in the present application is generated by the MAC302 or MAC352.
[0374] As an embodiment, the first signaling in the present application is generated in the PHY301 or PHY351.
[0375] As an embodiment, the first MAC PDU in the present application is generated in the RRC306.
[0376] As an embodiment, the first MAC PDU in the present application is generated in the PDCP 304 or PDCP354.
[0377] As an embodiment, the first MAC PDU in the present application is generated in the RLC 303 or RLC 353.
[0378] As an embodiment, the first MAC PDU in the present application is generated by the MAC302 or MAC352.
[0379] Example 4
[0380] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in the attached figure. Figure 4 shown. Figure 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.
[0381] The first communication 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.
[0382] The second communication device 410 includes a controller / processor 475 , a memory 476 , a receive processor 470 , a transmit processor 416 , a multi-antenna receive processor 472 , a multi-antenna transmit processor 471 , a transmitter / receiver 418 and an antenna 420 .
[0383] In 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 transmission from the second communication device 410 to the first communication 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 communication 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 constellations 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 processing on the coded and modulated symbols to generate one or more spatial streams. The transmit processor 416 then maps each spatial stream to a subcarrier, multiplexes it with a reference signal (e.g., a pilot) in the time domain and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying a time-domain multi-carrier symbol stream. The multi-antenna transmit processor 471 then performs a transmit analog precoding / beamforming operation 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, and then provides it to a different antenna 420.
[0384] In the transmission from the second communication device 410 to the first communication device 450, at the first communication device 450, each receiver 454 receives a signal through its corresponding antenna 452. Each receiver 454 recovers the information modulated onto the RF carrier and converts the RF stream into a baseband multi-carrier symbol stream and provides it to the receiving processor 456. The receiving processor 456 and the multi-antenna receiving processor 458 implement various signal processing functions of the L1 layer. The multi-antenna receiving processor 458 performs a receiving analog precoding / beamforming operation on the baseband multi-carrier symbol stream from the receiver 454. The receiving processor 456 uses a fast Fourier transform (FFT) to convert the baseband multi-carrier symbol stream after the receiving analog precoding / beamforming operation from the time domain to the frequency domain. In the frequency domain, the physical layer data signal and the reference signal are demultiplexed by the receiving processor 456, wherein the reference signal will be used for channel estimation, and the data signal is recovered after multi-antenna detection in the multi-antenna receiving processor 458 to any spatial stream destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receiving processor 456, and soft decisions are generated. The receiving processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second communication device 410 on the physical channel. The upper layer data and control signals are then provided to the 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. The memory 460 may be referred to as a computer-readable medium. In the transmission from the second communication device 410 to the second communication device 450, the controller / processor 459 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover the upper layer data packets from the core network. The upper layer data packets are then provided to all protocol layers above the L2 layer. Various control signals may also be provided to L3 for L3 processing.
[0385] In the transmission from the first communication device 450 to the second communication device 410, at the first communication device 450, a data source 467 is used to provide upper layer data packets to the controller / processor 459. The data source 467 represents all protocol layers above the L2 layer. Similar to the transmission function at the second communication device 410 described in the transmission from the second communication device 410 to the first communication device 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, and implements L2 layer functions for user plane and control plane. The controller / processor 459 is also responsible for the retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding processing, and the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based precoding and non-codebook-based precoding, and beamforming processing. Then, the transmit processor 468 modulates the generated spatial stream into a multi-carrier / single-carrier symbol stream, which is then provided to different antennas 452 via the transmitter 454 after analog precoding / beamforming operations 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 then provides it to the antenna 452.
[0386] In the transmission from the first communication device 450 to the second communication device 410, the function at the second communication device 410 is similar to the reception function 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 a radio frequency signal through its corresponding antenna 420, converts the received radio frequency signal into a baseband signal, and provides the baseband signal to the multi-antenna reception processor 472 and the reception processor 470. The reception processor 470 and the multi-antenna reception processor 472 jointly 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 storing program codes and data. The memory 476 can be referred to as a computer-readable medium. In the transmission from the first communication device 450 to the second communication device 410, the controller / processor 475 provides multiplexing between transport and logical channels, packet reassembly, decryption, header decompression, control signal processing to recover the upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.
[0387] As an embodiment, the first communication device 450 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used together with the at least one processor, and the first communication device 450 at least: constructs a first MAC PDU; sends the first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load; wherein the first field is a field in the first MAC sub-header other than the LCID field; the first MAC load is not the first status report.
[0388] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, wherein the computer-readable instruction program generates actions when executed by at least one processor, and the actions include: forming a first MAC PDU; sending the first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load; wherein the first field is a field in the first MAC sub-header other than the LCID field; the first MAC load is not the first status report.
[0389] As an embodiment, the second communication device 410 includes: at least one processor and at least one memory, the at least one memory including computer program code; the at least one memory and the computer program code are configured to be used with the at least one processor. The second communication device 410 at least: receives a first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load; wherein the first MAC PDU is constructed; the first field is a field in the first MAC sub-header other than the LCID field; the first MAC load is not the first status report.
[0390] As an embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generates actions when executed by at least one processor, the actions including: receiving a first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load; wherein the first MAC PDU is constructed; the first field is a field in the first MAC sub-header other than the LCID field; the first MAC load is not the first status report.
[0391] As an embodiment, the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 are used to receive the first signaling; and at least one of the antenna 420, the transmitter 418, the transmitting processor 416, and the controller / processor 475 is used to send the first signaling.
[0392] As an implementation, the antenna 452, the transmitter 454, the transmit processor 468, and the controller / processor 459 are used to send a first MAC PDU; and at least one of the antenna 420, the receiver 418, the receive processor 470, and the controller / processor 475 is used to receive a first MAC PDU.
[0393] As an implementation, the antenna 452, the transmitter 454, the transmit processor 468, and the controller / processor 459 are used to send a first message; and at least one of the antenna 420, the receiver 418, the receive processor 470, and the controller / processor 475 is used to receive a first message.
[0394] As an embodiment, the first communication device 450 corresponds to the first node in this application.
[0395] As an embodiment, the second communication device 410 corresponds to the second node in this application.
[0396] As an embodiment, the first communication device 450 is a user equipment.
[0397] As an embodiment, the first communication device 450 is a user equipment supporting a large delay difference.
[0398] As an embodiment, the first communication device 450 is a user equipment supporting NTN.
[0399] As an embodiment, the first communication device 450 is an aircraft device.
[0400] As an embodiment, the first communication device 450 has a positioning capability.
[0401] As an embodiment, the first communication device 450 does not have a fixed energy capability.
[0402] As an embodiment, the first communication device 450 is a user equipment supporting TN.
[0403] As an embodiment, the first communication device 450 is an Internet of Things terminal.
[0404] As an embodiment, the first communication device 450 is a V2X terminal.
[0405] As an embodiment, the second communication device 410 is a base station device (gNB / eNB / ng-eNB).
[0406] As an embodiment, the second communication device 410 is a base station device supporting a large delay difference.
[0407] As an embodiment, the second communication device 410 is a base station device supporting NTN.
[0408] As an embodiment, the second communication device 410 is a satellite device.
[0409] As an embodiment, the second communication device 410 is a flying platform device.
[0410] As an embodiment, the second communication device 410 is a base station device supporting TN.
[0411] As an embodiment, the second communication device 410 is a user equipment.
[0412] Example 5
[0413] Embodiment 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in the attached Figure 5 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.
[0414] for First node U01 In step S5101, a first signaling is received; in step S5102, a first MAC PDU is constructed; in step S5103, the first MAC PDU is sent.
[0415] for Second node N02 , in step S5201, the first signaling is sent; in step S5202, the first MAC PDU is received.
[0416] In Example 5, the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load; the first field is a field in the first MAC sub-header other than the LCID field; the first MAC load is not the first status report; and 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.
[0417] As an 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 field is used to indicate whether the first MAC sub-PDU includes a first status report.
[0418] As an 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.
[0419] As an embodiment, the phrase that 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 not used to indicate whether the first MAC sub-PDU includes a first status report.
[0420] As an embodiment, the first signaling is transmitted via an air interface.
[0421] As an embodiment, the first signaling is sent through an antenna port.
[0422] As an embodiment, the first signaling includes an uplink (UL) signal.
[0423] As an embodiment, the first signaling includes a sidelink (Sidelink, SL) signal.
[0424] As an embodiment, the first signaling includes an RRC message.
[0425] As an embodiment, the first signaling includes an RRCRelease message or an RRCConnectionRelease.
[0426] As an embodiment, the first signaling includes at least one IE (Information Element) in an RRC message.
[0427] As an embodiment, the first signaling includes a field in an RRC message.
[0428] As a sub-embodiment of this embodiment, the RRC message includes RRCRelease or RRCConnectionRelease.
[0429] As a sub-embodiment of this embodiment, the RRC message includes SIB1 (System Information Block 1).
[0430] As a sub-embodiment of this embodiment, the RRC message includes RRCReconfiguration or RRCConnectionReconfiguration.
[0431] As a sub-embodiment of this embodiment, the one field is set to setup to indicate that the first field is used to indicate whether the first MAC sub-PDU includes a first status report.
[0432] 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.
[0433] As a sub-embodiment of this embodiment, the one field is set to release to indicate that the first field is used to indicate the length of the first MAC payload field.
[0434] As a sub-embodiment of this embodiment, the one field is set to true to indicate that the first field is used to indicate whether the first MAC sub-PDU includes a first status report.
[0435] 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 a first status report.
[0436] As a sub-embodiment of this embodiment, the one field is not set to indicate that the first field is used to indicate the length of the first MAC payload field.
[0437] 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.
[0438] As an embodiment, when the first domain is set to a first target value, the first MAC subheader includes the first status report.
[0439] As an embodiment, when the first domain is set to a second target value, the first MAC subheader does not include the first status report.
[0440] As an embodiment, the first status report belongs to the first MAC subheader.
[0441] As an embodiment, the phrase "the first status report belongs to the first MAC subheader" includes: a field in the first MAC subheader indicating the first status report.
[0442] As an embodiment, the phrase "the first status report belongs to the first MAC subheader" includes: the first MAC subheader includes the first status report.
[0443] As an embodiment, the phrase "the first status report belongs to the first MAC subheader" includes: the first status report is determined by the first MAC subheader.
[0444] As an embodiment, the phrase "the first status report belongs to the first MAC subheader" includes: a field used to indicate that the first status report belongs to the first MAC subheader.
[0445] As an embodiment, the phrase "the first status report belongs to the first MAC subheader" includes: the first MAC subheader includes a target domain, and the target domain includes the first status report.
[0446] As a sub-embodiment of this embodiment, the sentence "The first MAC subheader includes a target domain, and the target domain includes the first status report" includes: the first MAC subheader includes a target domain, the target domain includes a first status report domain, and the first status report domain includes the first status report.
[0447] As an embodiment, the phrase, the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report including: the first field in the first MAC subheader indicates whether the first MAC sub-PDU includes the target domain in the present application, and the target domain includes a first status report.
[0448] As a sub-embodiment of this embodiment, the target domain includes a first status report domain, and the first status report domain includes the first status report.
[0449] As a sub-embodiment of this embodiment, the target domain consists of a first status report domain, and the first status report domain includes the first status report.
[0450] As a sub-embodiment of this embodiment, the target domain consists of a first status report domain and other domains, and the first status report domain includes the first status report.
[0451] As a sub-embodiment of this embodiment, the name of the target field is Buffer Size.
[0452] As a sub-embodiment of this embodiment, the name of the target domain is Data Volume.
[0453] As a sub-embodiment of this embodiment, the name of the target field is Data Size.
[0454] As a sub-embodiment of this embodiment, the name of the target field is Inactive Buffer Size.
[0455] As a sub-embodiment of this embodiment, the name of the target field is SDT Buffer Size.
[0456] As a sub-embodiment of this embodiment, the name of the target field is IDT Buffer Size.
[0457] As a sub-embodiment of this embodiment, the target field is the L field in the first MAC subheader.
[0458] As a sub-embodiment of this embodiment, the target field is the buffer size field in the first MAC subheader.
[0459] As a sub-embodiment of this embodiment, the target domain is the data volume domain in the first MAC subheader.
[0460] As a sub-embodiment of this embodiment, the length of the target field is equal to 8 bits.
[0461] As a sub-embodiment of this embodiment, the length of the target field is equal to 9 bits.
[0462] As a sub-embodiment of this embodiment, the length of the target field is equal to 10 bits.
[0463] As a sub-embodiment of this embodiment, the length of the target field is equal to 16 bits.
[0464] As an embodiment, the first MAC sub-PDU includes a second MAC payload, and the second MAC payload includes the first status report.
[0465] As an embodiment, the second MAC payload does not belong to the first MAC subheader.
[0466] As an embodiment, the second MAC load is different from the first MAC load.
[0467] As an embodiment, the LCID field of the first MAC sub-PDU does not uniquely indicate the second MAC load.
[0468] As an embodiment, the second MAC payload is a MAC CE or a MAC SDU or padding.
[0469] As an embodiment, the second MAC payload is not assigned a dedicated LCID.
[0470] As an embodiment, the second MAC payload does not have a dedicated MAC subheader.
[0471] As an embodiment, the second MAC load domain is placed directly before the first MAC load domain.
[0472] As an embodiment, the first MAC load domain is placed directly before the second MAC load domain.
[0473] 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, when the first domain is set to a second target value, the first MAC sub-PDU does not include a second MAC payload.
[0474] As an embodiment, when the first domain is set to a first target value, the first MAC sub-PDU includes a second MAC payload.
[0475] As an embodiment, when the first domain is set to a second target value, the first MAC sub-PDU does not include a second MAC payload.
[0476] As an embodiment, the phrase that the first MAC sub-PDU includes a second MAC payload includes: the second MAC payload is part of the first MAC sub-PDU.
[0477] As an embodiment, the phrase that the first MAC sub-PDU includes the second MAC payload includes: the first MAC sub-PDU includes the first MAC subheader, the first MAC payload and the second MAC payload.
[0478] As an embodiment, the phrase "the first MAC sub-PDU includes a second MAC payload" includes: the first MAC sub-PDU includes a second MAC payload field, and the second MAC payload field includes the second MAC payload.
[0479] As an embodiment, the phrase said second MAC load includes said first status report includes: said second MAC load includes at least said first status report.
[0480] As an embodiment, the phrase "the second MAC load includes the first status report" includes: the first status report belongs to the second MAC load.
[0481] As an embodiment, the phrase said second MAC load includes said first status report includes: said second MAC load is said first status report.
[0482] As an embodiment, the phrase said second MAC payload includes said first status report includes: said first status report is part of said second MAC payload.
[0483] As an embodiment, the sentence "the first MAC sub-PDU includes a second MAC payload, and the second MAC payload includes the first status report" includes: the first MAC sub-PDU includes a second MAC payload field, the second MAC payload field includes the second MAC payload, and the second MAC payload includes the first status report.
[0484] As a sub-embodiment of this embodiment, the second MAC load field includes a first status report field, and the first status report field includes the first status report.
[0485] As a sub-embodiment of this embodiment, the second MAC load field is composed of a first status report field, and the first status report field includes the first status report.
[0486] As a sub-embodiment of this embodiment, the second MAC load field is composed of a first status report field and other fields, and the first status report field includes the first status report.
[0487] As an embodiment, the phrase, the second MAC payload includes the first status report includes: the second MAC payload is used to carry the first status report
[0488] As an embodiment, the phrase, the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report including: the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes the second MAC payload in the present application, and the second MAC payload includes the first status report.
[0489] As an embodiment, the phrase, the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report including: the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes the second MAC load field in the present application, and the second MAC load field includes a first status report.
[0490] As an embodiment, the phrase, the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes a first status report including: the first field in the first MAC subheader is used to indicate whether the first MAC sub-PDU includes the second MAC load field in the present application, the second MAC load field includes the second MAC load, and the second MAC load includes the first status report.
[0491] As an embodiment, the first MAC sub-PDU includes a second field, and the second field indicates the length of at least the first MAC payload, and the unit of the length is byte.
[0492] As a sub-embodiment of this embodiment, the length of the second field is equal to 7 bits.
[0493] 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.
[0494] As a sub-embodiment of this embodiment, the length of the second field is equal to 9 bits.
[0495] As a sub-embodiment of this embodiment, the length of the second field is equal to 15 bits.
[0496] 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.
[0497] 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.
[0498] 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.
[0499] As a sub-embodiment of this embodiment, the second field occupies one byte immediately following the L field in the first MAC subheader.
[0500] 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.
[0501] 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.
[0502] As a sub-embodiment of this embodiment, the second field occupies one byte immediately following the L field in the first MAC subheader.
[0503] As a sub-embodiment of this embodiment, the phrase that the second field indicates at least the length of the first MAC payload includes: the second field indicates the length of the first MAC payload.
[0504] As a sub-embodiment of this embodiment, the phrase that the second field indicates the length of at least the first MAC payload includes: the second field indicates the length of the first MAC payload and the second MAC payload.
[0505] As a sub-embodiment of this embodiment, the first MAC subheader consists of the first field, the LCID field, and the second field.
[0506] As an embodiment, the first MAC subheader includes at least a first field, a second field and an LCID field.
[0507] As an embodiment, the second field is not included in the first MAC sub-PDU.
[0508] As an embodiment, the dashed box F5.1 is optional.
[0509] As an embodiment, the dashed box F5.1 exists.
[0510] As an embodiment, the dotted box F5.1 does not exist.
[0511] Example 6
[0512] Embodiment 6 illustrates a flowchart of wireless signal transmission according to another embodiment of the present application, as shown in the attached Figure 6 It is particularly noted that the order in this example does not limit the signal transmission order and implementation order in this application.
[0513] for First node U01 In step S6101, a first signaling is received; in step S6102, a first DRB is restored along with a first message; in step S6103, a first message is sent; in step S6104, a first DRB is restored along with the first message; in step S6105, a first condition set is met; in step S6106, a first status report is triggered as a response to the first condition set being met; in step S6107, a first MAC PDU is constructed; in step S6108, a first MAC PDU is sent.
[0514] for Second node N02 In step S6201, the first signaling is sent; in step S6202, the first message is received; in step S6203, the first MAC PDU is received.
[0515] In Example 6, the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load; the first field is a field in the first MAC sub-header other than the LCID field; the first MAC load is not the first status report; the first message is used for a first RRC recovery process; the first condition set includes that the first RRC recovery process is being executed and a first data block is effective, and the first data block is associated with the first DRB; the first status report indicates a cache-related status; and 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.
[0516] As an embodiment, the first message is sent in an RRC inactive (RRC_INACTIVE) state.
[0517] As an embodiment, the first message is sent in the RRC idle (RRC_IDLE) state.
[0518] As an embodiment, the first message is transmitted via an air interface.
[0519] As an embodiment, the first message is sent through an antenna port.
[0520] As an embodiment, the first message includes an uplink (UL) signal.
[0521] As an embodiment, the first message includes a sidelink (SL) signal.
[0522] As an embodiment, the first message is transmitted via SRB0 (Signalling Radio Bearer 0).
[0523] As an embodiment, the first message is transmitted via SRB1 (Signalling Radio Bearer 1).
[0524] As an embodiment, the first message is transmitted via SRB2 (Signalling Radio Bearer 2).
[0525] As an embodiment, the first message is transmitted via SRB3 (Signalling Radio Bearer 3).
[0526] As an embodiment, the first message is transmitted via CCCH (Common Control Channel).
[0527] As an embodiment, the first message is transmitted via DCCH (Common Control Channel).
[0528] As an embodiment, the first message includes an RRC (Radio Resource Control) message.
[0529] As an embodiment, the first message includes at least one IE (Information Element) in an RRC message.
[0530] As an embodiment, the first message includes at least one field in an RRC message.
[0531] As an embodiment, the first message includes a MAC (Medium Access Control) PDU (Protocol Data Unit), the MAC PDU includes a MAC SDU (Service Data Unit), and the MAC SDU carries an RRC message.
[0532] As a sub-embodiment of this embodiment, the one MAC SDU includes a CCCH SDU.
[0533] As a sub-embodiment of this embodiment, the one MAC SDU includes a DCCH SDU.
[0534] As a sub-embodiment of this embodiment, the one MAC SDU includes a DTCH (Dedicated Traffic Channel) SDU.
[0535] As an embodiment, the first message includes a RRCResumeRequest message or a RRCResumeRequest1 message.
[0536] As an embodiment, the first message includes an RRCConnectionResumeRequest message or an RRC EarlyDataRequest message.
[0537] As an embodiment, the first message includes an RRC message whose name includes at least one of RRC or Connection or Resume or sdt or idt or Inactive or Small or Data or Transmission or Request.
[0538] As an embodiment, the first message includes an RRCReconfigurationSidelink message.
[0539] As an embodiment, the first message includes a MCGFailureInformation message, or a RRCRestabilshmentRequest message, or a RRCSetupRequest message.
[0540] As an embodiment, the first message includes at least one of ShortI-RNTI-Value, or I-RNTI-Value, or resumeMAC-I, or resumeCause or spare.
[0541] As a sub-embodiment of this embodiment, the first message includes resumeMAC-I, and the resumeMAC-I is a bit string with a length equal to 16.
[0542] As a sub-embodiment of this embodiment, the first message includes resumeCause, and the resumeCause indicates one of emergency or highPriorityAccess or mt-Access or mo-Signalling or mo-Data or mo-VoiceCall or mo-VideoCall or mo-SMS or rna-Update or ps-PriorityAccess or mcs-PriorityAccess or sdt or idt or edt or smalldatatransmission or inactivedatatransmission or pur.
[0543] As an embodiment, the spare is a bit string with a length equal to 1.
[0544] As an embodiment, the first message is all or part of message 3 (Message 3, Msg3).
[0545] As an embodiment, the first message is all or part of message A (Message A, MsgA).
[0546] As an embodiment, the sentence "along with the first message, restore at least the first DRB" includes: when preparing to send the first message, restore at least the first DRB.
[0547] As an embodiment, the sentence "along with the first message, restoring at least the first DRB" includes: when the content of the first message is set to be completed, restoring at least the first DRB.
[0548] As an embodiment, the sentence "along with the first message, restore at least the first DRB" includes: after the first message is sent, restore at least the first DRB.
[0549] As an embodiment, the sentence "along with the first message, restore at least the first DRB" includes: when the content of the first message is set and before being submitted to a lower layer, restore at least the first DRB.
[0550] As an embodiment, the first DRB includes at least one DRB.
[0551] As an embodiment, the first DRB is used for SDT.
[0552] As an embodiment, the first DRB is used for IDT (Inactive Data Transmission).
[0553] As an embodiment, the first DRB is used for EDT (Early Data Transmission).
[0554] As an embodiment, the first DRB is associated with a PDCP (Packet Data Convergence Protocol) entity.
[0555] As an embodiment, the first DRB is configured via an RRC message.
[0556] As an embodiment, the first DRB is configured via a SIB1 message.
[0557] As an embodiment, the first DRB is configured through a RRCRelease message.
[0558] As an embodiment, the first DRB is configured through an RRCConnectionRelease message.
[0559] As an embodiment, the first DRB includes a DRB configured to be recovered in an RRC inactive state.
[0560] As an embodiment, the recovery means resume.
[0561] As an embodiment, the sentence “in response to a first set of conditions being met, triggering the first status report” includes: when the first set of conditions is met, triggering the first status report.
[0562] As an embodiment, the sentence “as a response to a first set of conditions being satisfied, triggering the first status report” includes: the first status report is triggered by the first status set.
[0563] As an embodiment, the first RRC recovery process is used for the SDT process.
[0564] As an embodiment, the first RRC recovery process includes an RRC recovery process.
[0565] As an embodiment, the first RRC recovery process includes recovering a suspended RRC connection.
[0566] As an embodiment, the first RRC recovery process includes sending the first data block in an RRC inactive state.
[0567] As an embodiment, the phrase that the first RRC recovery procedure is being executed includes: a timer is running.
[0568] As a sub-embodiment of this embodiment, the one timer is not T319.
[0569] As a sub-embodiment of this embodiment, the timer is started along with the first message.
[0570] As a sub-embodiment of this embodiment, when an RRC message is received and the RRC message is a response to the first message, the first timer is stopped.
[0571] As a subsidiary embodiment of this sub-embodiment, the RRC message includes one of an RRCRelease message, or an RRCResume message, or an RRCSetup message, or an RRCReject message, or an RRCConnectionRelease message, or an RRCConnectionResume message, or an RRCConnectionSetup message, or an RRCConnectionReject message, or an RRCCEarlyDataComplete message.
[0572] As a subsidiary embodiment of this sub-embodiment, the name of the RRC message includes at least one of RRC or Connection or Resume or Release or Resume or RRCReject or Setup or Reconfiguration or Complete or sdt or idt or Inactive or Small or Data or Transmission.
[0573] As a sub-embodiment of this embodiment, the first timer being running means that the first timer is started and the timing of the first timer has not reached the expiration value of the first timer.
[0574] As a sub-embodiment of this embodiment, the first timer being running refers to the first time is running.
[0575] As a sub-embodiment of this embodiment, the first timer being running means that the timing of the first timer is not equal to 0 and is not equal to the expiration value of the first timer.
[0576] As an embodiment, the phrase that the first RRC recovery procedure is being executed includes: sending a preamble code sequence used for SDT and monitoring a PDCCH scrambled by MSGB-RNTI or TEMPORARY_C-RNTI or C-RNTI.
[0577] As an embodiment, the phrase that the first RRC recovery procedure is being executed includes: using pre-configured resources used for SDT.
[0578] As an embodiment, the sentence "the first condition set includes that the first RRC recovery process is being executed and the first data block is effective" includes: when the first RRC recovery process is being executed and the first data block is effective, the first condition set is satisfied.
[0579] As an embodiment, the sentence "the first condition set includes that the first RRC recovery process is being executed and the first data block is effective" includes: at least the first RRC recovery process is being executed, and the first data block effectiveness is used to determine that the first condition set is met.
[0580] As an embodiment, the phrase "the first data block is effective" includes: the first data block is available to the MAC entity.
[0581] As an embodiment, the phrase "the first data block takes effect" includes: the first data block reaches at least one of the MAC layer, the RLC layer, or the PDCP layer.
[0582] As an embodiment, the phrase "first data block is effective" includes: the first data block is ready to be sent.
[0583] As an embodiment, the phrase "the first data block is effective" includes: the first data block is generated but no resources are allocated.
[0584] As an embodiment, the phrase the first data block is associated with the first DRB includes: the first data block is mapped to the first DRB.
[0585] As an embodiment, the phrase "the first data block is associated with the first DRB" includes: the first data block is not data of the SRB.
[0586] As an embodiment, the dashed box F6.1 is optional.
[0587] As an embodiment, the dashed box F6.2 is optional.
[0588] As an embodiment, the dashed box F6.3 is optional.
[0589] As an embodiment, the dashed box F6.1 exists.
[0590] As an embodiment, the dotted box F6.1 does not exist.
[0591] As an embodiment, the dashed box F6.2 exists.
[0592] As an embodiment, the dotted box F6.2 does not exist.
[0593] As an embodiment, the dashed box F6.3 exists.
[0594] As an embodiment, the dotted box F6.3 does not exist.
[0595] As an embodiment, one of the dashed box F6.2 and the dashed box F6.3 exists.
[0596] As an embodiment, the dotted box F6.2 exists, and the dotted box F6.3 does not exist.
[0597] As an embodiment, the dotted box F6.2 does not exist, and the dotted box F6.3 exists.
[0598] Example 7
[0599] 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 the attached Figure 7 As shown in the attached Figure 7 In the example, a box represents a MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC SDU or a MAC CE or a padding or a field or multiple fields; it is particularly noted that a box in another box in this example represents that the other box contains the box, and the size and position relationship between the one box and the other box does not limit the specific format of the first MAC PDU of the present application.
[0600] In embodiment 7, the first status report belongs to the first MAC subheader 702.
[0601] As an embodiment, the first transmitter forms a first MAC PDU 701; sends the first MAC PDU 701; the first MAC PDU 701 includes a first MAC sub-PDU 702, the first MAC sub-PDU 702 includes a first MAC sub-header 703, the first MAC sub-header 703 includes 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 includes a first status report, and the LCID field 705 of the first MAC sub-PDU 702 is used to indicate the first MAC load; wherein the first field 704 is a field in the first MAC sub-header 703 other than the LCID field 705; the first MAC load is not the first status report; the first status report belongs to the first MAC sub-header 703.
[0602] As an embodiment, the first MAC subheader 703 includes the first status report field 706, and the first status report field 706 includes the first status report.
[0603] As an embodiment, the first MAC subheader 703 also includes an eLCID field.
[0604] As a sub-embodiment of this embodiment, the LCID field is set to 33 or 34.
[0605] As an embodiment, the first MAC subheader 703 does not include the eLCID field.
[0606] As a sub-embodiment of this embodiment, the LCID field is not set to 33 or 34.
[0607] As an embodiment, the first MAC subheader 703 also includes an R field.
[0608] As an embodiment, the first MAC subheader 703 does not include the R field.
[0609] As an embodiment, the first MAC subheader 703 also includes the second domain in this application.
[0610] As an embodiment, the first MAC subheader 703 does not include the second domain in this application.
[0611] As an embodiment, the first MAC subheader 703 also includes a format field.
[0612] As an embodiment, the first MAC subheader 703 does not include a format field.
[0613] As an embodiment, the first MAC subheader 703 also includes a length (Length, L) field.
[0614] As an embodiment, the first MAC subheader 703 does not include a length (Length, L) field.
[0615] Example 8
[0616] 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 the attached Figure 8 As shown in the attached Figure 8 In the example, a box represents a MAC PDU or a MAC sub-PDU or a MAC sub-header or a MAC SDU or a MAC CE or a padding or a field or multiple fields; it is particularly noted that a box in another box in this example represents that the other box contains the box, and the size and position relationship between the one box and the other box does not limit the specific format of the first MAC PDU of the present application.
[0617] In Embodiment 8, the first MAC sub-PDU 802 includes a second MAC payload, and the second MAC payload includes the first status report.
[0618] As an embodiment, the first transmitter forms a first MAC PDU 801; sends the first MAC PDU 801; the first MAC PDU 801 includes a first MAC sub-PDU 802, the first MAC sub-PDU 802 includes a first MAC sub-header 803, the first MAC sub-header 803 includes at least a first field 804 and an LCID field 805, the first field 804 in the first MAC sub-header 803 is used to indicate whether the first MAC sub-PDU 802 includes a first status report, and the LCID field 805 of the first MAC sub-PDU 802 is used to indicate the first MAC load; wherein the first field 804 is a field in the first MAC sub-header 803 other than the LCID field 804; the first MAC load is not the first status report; the first MAC sub-PDU 802 includes a second MAC load, and the second MAC load includes the first status report.
[0619] As an embodiment, the phrase: the first MAC sub-PDU 802 includes a second MAC load, and the second MAC load includes the first status report includes: the first MAC sub-PDU 802 includes a second MAC load field 808, and the second MAC load field 808 includes the first status report.
[0620] As an embodiment, the phrase "the first MAC sub-PDU 802 includes a second MAC load, and the second MAC load includes the first status report including: the first MAC sub-PDU 802 includes a second MAC load field 808, the second MAC load field 808 includes the first status report field 807, and the first status report field 807 includes the first status report.
[0621] As an embodiment, the first MAC subheader 803 also includes an eLCID field.
[0622] As an embodiment, the first MAC subheader 803 does not include the eLCID field.
[0623] As an embodiment, the first MAC subheader 803 also includes a reserved (R) field.
[0624] As an embodiment, the first MAC subheader 803 does not include a reserved (R) field.
[0625] As an embodiment, the first MAC subheader 803 also includes the second domain in this application.
[0626] As an embodiment, the first MAC subheader 803 does not include the second field in this application.
[0627] As an embodiment, the first MAC subheader 803 also includes a format (Format, F) field.
[0628] As an embodiment, the first MAC subheader 803 does not include a format (Format, F) field.
[0629] As an embodiment, the first MAC subheader 803 also includes a length (Length, L) field.
[0630] As an embodiment, the first MAC subheader 803 does not include a length (Length, L) field.
[0631] Example 9
[0632] Embodiment 9 illustrates a schematic diagram of the format of the first MAC sub-PDU according to an embodiment of the present application, as shown in the attached Fig. 9 As shown in the attached Fig. 9 In the example, the ellipsis represents other MAC sub-PDUs in the first MAC PDU except the first MAC sub-PDU; a box represents a MAC sub-PDU or a MAC sub-header or a MAC SDU or a MAC CE or a padding or a field or multiple fields; it is particularly noted that a box in another box in this example means that the other box contains the box, and the size and position relationship between the one box and the other box does not limit the specific format of the first MAC PDU of the present application.
[0633] In Example 9, the first MAC sub-PDU 901 includes the first MAC sub-header 902 and the first MAC load field 907; the first MAC sub-header 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.
[0634] As an embodiment, the first field 905 in the first MAC subheader 902 is used to indicate that the first MAC sub-PDU 901 includes a first status report.
[0635] As an embodiment, the first transmitter forms a first MAC PDU; sends the first MAC PDU; the first MAC PDU includes a first MAC sub-PDU 901, the first MAC sub-PDU 901 includes a first MAC sub-header 902, the first MAC sub-header 902 includes 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 includes a first status report, and the LCID field 906 of the first MAC sub-PDU 901 is used to indicate the first MAC load; wherein the first field 905 is a field in the first MAC sub-header 902 other than the LCID field 906; the first MAC load includes the first status report 904; the first status report belongs to the first MAC sub-header 902.
[0636] As an embodiment, the ellipsis on the left side of the first MAC sub-PDU 901 does not exist, and the ellipsis on the right side of the first MAC sub-PDU 901 exists.
[0637] As an embodiment, the ellipsis on the left side of the first MAC sub-PDU 901 exists, and the ellipsis on the right side of the first MAC sub-PDU 901 does not exist.
[0638] As an embodiment, both the ellipsis on the left side of the first MAC sub-PDU 901 and the ellipsis on the right side of the first MAC sub-PDU 901 exist.
[0639] As an embodiment, the ellipsis on the left side of the first MAC sub-PDU 901 and the ellipsis on the right side of the first MAC sub-PDU 901 do not exist.
[0640] As an embodiment, the first MAC load field 907 indicates the first MAC load.
[0641] As an embodiment, the first MAC load domain 907 carries the first MAC load.
[0642] As an embodiment, the first MAC load domain 907 includes the first MAC load.
[0643] As an embodiment, the first status report field 904 indicates the first status report.
[0644] As an embodiment, the first status report field 904 carries the first status report.
[0645] As an embodiment, the first status report field 904 includes the first status report.
[0646] As an embodiment, box 903 includes the fields in the first MAC subheader 902 .
[0647] As an embodiment, the box 903 includes at least the first field 905 , the LCID field 906 and the first status report field 904 .
[0648] As an embodiment, the box 903 also includes an eLCID domain.
[0649] As an embodiment, the block 903 does not include the eLCID field.
[0650] As an embodiment, the block 903 also includes a reserved (R) field.
[0651] As an embodiment, the block 903 does not include a reserved (R) field.
[0652] As an embodiment, the box 903 also includes the second domain in the present application.
[0653] As an embodiment, the block 903 does not include the second domain in the present application.
[0654] As an embodiment, the box 903 also includes a format (Format, F) field.
[0655] As an embodiment, the box 903 does not include a format (Format, F) field.
[0656] As an embodiment, the block 903 also includes a length (Length, L) field.
[0657] As an embodiment, the block 903 does not include a length (Length, L) field.
[0658] Example 10
[0659] Embodiment 10 illustrates a schematic diagram of the format of the first MAC sub-PDU according to another embodiment of the present application, as shown in the attached Fig.10 As shown in the attached Fig.10In the example, the ellipsis represents other MAC sub-PDUs in the first MAC PDU except the first MAC sub-PDU; a box represents a MAC sub-PDU or a MAC sub-header or a MAC SDU or a MAC CE or a padding or a field or multiple fields; it is particularly noted that a box in another box in this example means that the other box contains the box, and the size and position relationship between the one box and the other box does not limit the specific format of the first MAC PDU of the present application.
[0660] In embodiment 10, the first MAC sub-PDU 1001 includes the first MAC sub-header 1002, the second MAC load field 1006 and the first MAC load field 1009; the first MAC sub-header 1002 includes the first field 1004 and the LCID field 1005; the second MAC load field 1006 includes the first status report field 1008, the second MAC load field 1006 includes the second MAC load, the first MAC load field 1009 includes the first MAC load, and the first status report field 1008 includes the first status report.
[0661] As an embodiment, the first field 1004 in the first MAC subheader 1002 is used to indicate that the first MAC sub-PDU 1001 includes a first status report.
[0662] As an embodiment, the first transmitter forms a first MAC PDU; sends the first MAC PDU; the first MAC PDU includes a first MAC sub-PDU 1001, the first MAC sub-PDU 1001 includes a first MAC sub-header 1002, the first MAC sub-header 1002 includes 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 includes a first status report, and the LCID field 1005 of the first MAC sub-PDU 1001 is used to indicate the first MAC load; wherein the first field 1004 is a field in the first MAC sub-header 1002 other than the LCID field 1005; the first MAC load is not the first status report; the first MAC sub-PDU 1001 includes a second MAC load, and the second MAC load includes the first status report.
[0663] As an embodiment, the ellipsis on the left side of the first MAC sub-PDU 1001 does not exist, and the ellipsis on the right side of the first MAC sub-PDU 1001 exists.
[0664] As an embodiment, the ellipsis on the left side of the first MAC sub-PDU 1001 exists, and the ellipsis on the right side of the first MAC sub-PDU 1001 does not exist.
[0665] As an embodiment, both the ellipsis on the left side of the first MAC sub-PDU 1001 and the ellipsis on the right side of the first MAC sub-PDU 1001 exist.
[0666] As an embodiment, the ellipsis on the left side of the first MAC sub-PDU 1001 and the ellipsis on the right side of the first MAC sub-PDU 1001 do not exist.
[0667] As an embodiment, the first MAC load field 1009 indicates the first MAC load.
[0668] As an embodiment, the first MAC load domain 1009 carries the first MAC load.
[0669] As an embodiment, the first MAC load domain 1009 includes the first MAC load.
[0670] As an embodiment, the second MAC load field 1006 indicates the second MAC load.
[0671] As an embodiment, the second MAC load domain 1006 carries the second MAC load.
[0672] As an embodiment, the second MAC load domain 1006 includes the second MAC load.
[0673] As an embodiment, the first status report field 1008 indicates the first status report.
[0674] As an embodiment, the first status report field 1008 carries the first status report.
[0675] As an embodiment, the first status report field 1008 includes the first status report.
[0676] As an embodiment, box 1003 includes the fields in the first MAC subheader 1002 .
[0677] As an embodiment, the box 1003 includes at least the first domain 1004 and the LCID domain 1005.
[0678] As an embodiment, the box 1003 also includes an eLCID domain.
[0679] As an embodiment, the block 1003 does not include the eLCID field.
[0680] As an embodiment, the box 1003 also includes a reserved (R) field.
[0681] As an embodiment, the block 1003 does not include a reserved (R) field.
[0682] As an embodiment, the box 1003 also includes the second domain in the present application.
[0683] As an embodiment, the box 1003 does not include the second domain in the present application.
[0684] As an embodiment, the box 1003 also includes a format (Format, F) field.
[0685] As an embodiment, the box 1003 does not include a format (Format, F) field.
[0686] As an embodiment, the block 1003 also includes a length (Length, L) field.
[0687] As an embodiment, the block 1003 does not include a length (Length, L) field.
[0688] As an embodiment, block 1007 includes a domain in the second MAC load domain.
[0689] As an embodiment, the box 1007 includes at least the first status report field.
[0690] As an embodiment, the box 1007 also includes other fields in the present application.
[0691] As an embodiment, the box 1007 does not include other fields in the present application.
[0692] Embodiment 11
[0693] Embodiment 11 illustrates a schematic diagram of the format of the first MAC sub-PDU according to another embodiment of the present application, as shown in the attached Fig.11 As shown in the attached Fig.11In the example, the ellipsis represents other MAC sub-PDUs in the first MAC PDU except the first MAC sub-PDU; a box represents a MAC sub-PDU or a MAC sub-header or a MAC SDU or a MAC CE or a padding or a field or multiple fields; it is particularly noted that a box in another box in this example means that the other box contains the box, and the size and position relationship between the one box and the other box does not limit the specific format of the first MAC PDU of the present application.
[0694] In Embodiment 11, the first MAC sub-PDU 1101 includes the first MAC sub-header 1102 and the first MAC load field 1106; the first MAC sub-header 1102 includes the first field 1104 and the LCID field 1105; and the first MAC load field 1106 includes the first MAC load.
[0695] As an embodiment, the first field 1104 in the first MAC subheader 1102 is used to indicate that the first MAC sub-PDU 1101 does not include a first status report.
[0696] As an embodiment, the first transmitter forms a first MAC PDU; sends the first MAC PDU; the first MAC PDU includes a first MAC sub-PDU 1101, the first MAC sub-PDU 1101 includes a first MAC sub-header 1102, the first MAC sub-header 1102 includes at least a first field 1104 and an LCID field 1105, the first field 1104 in the first MAC sub-header 1102 is used to indicate that the first MAC sub-PDU 1101 does not include a first status report, and 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 in the first MAC sub-header 1102 other than the LCID field 1105; and the first MAC load is not the first status report.
[0697] As a sub-embodiment of this embodiment, when the first field 1104 in the first MAC sub-header 1102 is used to indicate that the first MAC sub-PDU 1101 includes a first status report, the first status report belongs to the first MAC sub-header 1102 .
[0698] 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 sub-PDU 1101 includes a first status report, the first MAC sub-PDU 1101 includes a second MAC payload, and the second MAC payload includes the first status report.
[0699] As an embodiment, the ellipsis on the left side of the first MAC sub-PDU 1101 does not exist, and the ellipsis on the right side of the first MAC sub-PDU 1101 exists.
[0700] As an embodiment, the ellipsis on the left side of the first MAC sub-PDU 1101 exists, and the ellipsis on the right side of the first MAC sub-PDU 1101 does not exist.
[0701] As an embodiment, both the ellipsis on the left side of the first MAC sub-PDU 1101 and the ellipsis on the right side of the first MAC sub-PDU 1101 exist.
[0702] As an embodiment, the ellipsis on the left side of the first MAC sub-PDU 1101 and the ellipsis on the right side of the first MAC sub-PDU 1101 do not exist.
[0703] As an embodiment, the first MAC load field 1106 indicates the first MAC load.
[0704] As an embodiment, the first MAC load domain 1106 carries the first MAC load.
[0705] As an embodiment, the first MAC load domain 1106 includes the first MAC load.
[0706] As an embodiment, box 1103 includes the fields in the first MAC subheader 1102 .
[0707] As an embodiment, the box 1103 includes at least the first domain 1104 and the LCID domain 1105.
[0708] As an embodiment, the box 1103 also includes an eLCID domain.
[0709] As an embodiment, the block 1103 does not include the eLCID field.
[0710] As an embodiment, the box 1103 also includes a reserved (R) field.
[0711] As an embodiment, the block 1103 does not include a reserved (R) field.
[0712] As an embodiment, the box 1103 also includes the second domain in the present application.
[0713] As an embodiment, the box 1103 does not include the second domain in the present application.
[0714] As an embodiment, the box 1103 also includes a format (Format, F) field.
[0715] As an embodiment, the box 1103 does not include a format (Format, F) field.
[0716] As an embodiment, the box 1103 also includes a length (Length, L) field.
[0717] As an embodiment, the block 1103 does not include a length (Length, L) field.
[0718] Example 12
[0719] Embodiment 12 illustrates a schematic diagram of a first MAC subheader according to the first embodiment of the present application, as shown in the attached Fig.12 As shown in the attached Fig.12 In the diagram, a box represents one or more domains.
[0720] In Example 12, 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; or the first MAC subheader includes the first field 1202, the LCID field 1201, the second field 1204 and the R field 1203; wherein the first status report belongs to the first MAC subheader.
[0721] As an embodiment, the target domain 1205 always exists.
[0722] As an embodiment, the target domain 1205 is optional.
[0723] As an embodiment, the target domain 1205 exists.
[0724] 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.
[0725] As a sub-implementation of this embodiment, the first MAC subheader is composed of the first field 1202, the LCID field 1201, the second field 1204, the target field 1205 and the R field 1203.
[0726] As a sub-implementation of this embodiment, when the first field 1202 is set to a first target value, the first MAC subheader consists of the first field 1202, the LCID field 1201, the second field 1204, the target field 1205 and the R field 1203.
[0727] As an embodiment, the target domain 1205 does not exist.
[0728] 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.
[0729] As a sub-implementation of this embodiment, the first MAC subheader consists of the first field 1202 , the LCID field 1201 , the second field 1204 and the R field 1203 .
[0730] As a sub-implementation of this embodiment, when the first field 1202 is set to a second target value, the first MAC subheader consists of the first field 1202 , the LCID field 1201 , the second field 1204 and the R field 1203 .
[0731] As an embodiment, the R domain 1203, the first domain 1202 and the LCID domain 1201 occupy the first byte (Oct 1), and the sum of the lengths of the R domain, the first domain 1202 and the LCID domain 1201 is equal to one byte.
[0732] As an embodiment, the second field 1204 occupies the second byte (Oct 2), and the length of the second field 1204 is equal to one byte.
[0733] As an embodiment, when the target domain 1205 exists, the target domain 1205 occupies the third byte (Oct 3), and the length of the target domain 1205 is equal to one byte.
[0734] As an embodiment, the length of the second field 1204 is equal to one byte.
[0735] As an embodiment, the second domain 1204 is placed directly after the LCID domain.
[0736] As an embodiment, the target field 1205 is placed directly after the LCID field.
[0737] As an embodiment, the R domain 1203 is placed directly before the first domain 1202.
[0738] As an embodiment, the first domain 1202 is placed directly before the R domain 1203.
[0739] As an embodiment, the R field 1203 is the highest bit in the first MAC subheader.
[0740] As an embodiment, the first domain 1202 is placed directly after the R domain and before the LCID domain.
[0741] Example 13
[0742] Embodiment 13 illustrates a schematic diagram of a first MAC subheader according to the second embodiment of the present application, as shown in the attached Fig.13 As shown in the attached Fig.13 In the diagram, a box represents one or more domains.
[0743] In embodiment 13, the first MAC subheader includes the first domain 1302, the LCID domain 1301, the second domain 1303, the second domain 1304 and the target domain 1305; or the first MAC subheader includes the first domain 1302, the LCID domain 1301, the second domain 1303 and the second domain 1304; wherein the first status report belongs to the first MAC subheader.
[0744] As an embodiment, the target domain 1305 always exists.
[0745] As an embodiment, the target domain 1305 is optional.
[0746] As an embodiment, the target domain 1305 exists.
[0747] 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 target field 1305.
[0748] As a sub-implementation of this embodiment, the first MAC subheader consists of the first field 1302 , the LCID field 1301 , the second field 1303 , the second field 1304 and the target field 1305 .
[0749] As a sub-implementation of this embodiment, when the first field 1302 is set to a first target value, the first MAC subheader consists of the first field 1302 , the LCID field 1301 , the second field 1303 , the second field 1304 and the target field 1305 .
[0750] As an embodiment, the target domain 1305 does not exist.
[0751] 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.
[0752] As a sub-implementation of this embodiment, the first MAC subheader consists of the first field 1302 , the LCID field 1301 , the second field 1303 and the second field 1304 .
[0753] As a sub-implementation of this embodiment, when the first field 1302 is set to a second target value, the first MAC subheader consists of the first field 1302 , the LCID field 1301 , the second field 1303 and the second field 1304 .
[0754] As an embodiment, the second domain 1303, the first domain 1302 and the LCID domain 1301 occupy the first byte (Oct 1), and the sum of the lengths of the second domain 1303, the first domain 1302 and the LCID domain 1301 is equal to one byte.
[0755] As an embodiment, the second field 1304 occupies the second byte (Oct 2), and the length of the second field 1304 is equal to one byte.
[0756] As an embodiment, when the target domain 1305 exists, the target domain 1305 occupies the third byte (Oct 3), and the length of the target domain 1305 is equal to one byte.
[0757] As an embodiment, the second domain 1303 and the second domain 1304 together constitute a domain.
[0758] As an embodiment, the second domain 1303 and the second domain 1304 are the same domain.
[0759] As an embodiment, the sum of the lengths of the second field 1303 and the second field 1304 is equal to 9 bits.
[0760] As an embodiment, the first domain 1302 is placed directly after the second domain 1303 .
[0761] As an embodiment, the second domain 1303 is placed directly after the first domain 1302.
[0762] Embodiment 14
[0763] Embodiment 14 illustrates a schematic diagram of a first MAC subheader according to the third embodiment of the present application, as shown in the attached Fig.14 As shown in the attached Fig.14 In the diagram, a box represents one or more domains.
[0764] 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.
[0765] As an embodiment, the target domain 1404 always exists.
[0766] As an embodiment, the target domain 1404 is optional.
[0767] As an example, the target domain 1404 exists.
[0768] 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 .
[0769] As a sub-embodiment of this embodiment, the first MAC subheader consists of an R field 1403 , a first field 1402 , an LCID field 1401 and a target field 1404 .
[0770] As a sub-embodiment of this embodiment, when the first field 1402 is set to the first target value, the first MAC subheader consists of an R field 1403 , a first field 1402 , an LCID field 1401 and a target field 1404 .
[0771] As an embodiment, the target domain 1404 does not exist.
[0772] As a sub-embodiment of this embodiment, the first MAC sub-header includes an R field 1403, a first field 1402 and an LCID field 1401.
[0773] As a sub-embodiment of this embodiment, the first MAC subheader consists of an R field 1403 , a first field 1402 and an LCID field 1401 .
[0774] As a sub-embodiment of this embodiment, when the first field 1402 is set to the second target value, the first MAC subheader consists of the R field 1403, the first field 1402 and the LCID field 1401.
[0775] As an embodiment, the R domain 1403, the first domain 1402 and the LCID domain 1401 occupy the first byte (Oct 1), and the sum of the lengths of the R domain 1403, the first domain 1402 and the LCID domain 1401 is equal to one byte.
[0776] As an embodiment, when the target domain 1404 exists, the target domain 1404 occupies the third byte (Oct 2), and the length of the target domain 1404 is equal to one byte.
[0777] As an embodiment, the first domain 1402 is placed directly after the R domain 1403.
[0778] As an embodiment, the R domain 1403 is placed directly after the first domain 1402.
[0779] Embodiment 15
[0780] Embodiment 15 illustrates a schematic diagram of a first MAC subheader according to the fourth embodiment of the present application, as shown in the attached Fig.15 As shown in the attached Fig.15 In the figure, a box represents one or more domains; the first domain 1502 and the LCID domain 1501 occupy the first byte (Oct 1), and the sum of the lengths of the first domain 1502 and the LCID domain 1501 is equal to one byte; the target domain 1503 occupies the second byte (Oct 2), and the length of the target domain 1503 is equal to one byte.
[0781] In embodiment 15, the first MAC subheader includes a first field 1502, an LCID field 1501 and a target field 1503; or the first MAC subheader includes a first field 1502 and an LCID field 1501; wherein the first status report belongs to the first MAC subheader.
[0782] As an embodiment, the length of the first field 1502 is equal to 2 bits.
[0783] As an embodiment, the target domain 1503 always exists.
[0784] As an embodiment, the target domain 1503 is optional.
[0785] As an embodiment, the target domain 1503 exists.
[0786] 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.
[0787] As a sub-embodiment of this embodiment, the first MAC subheader consists of the first domain 1502 , the LCID domain 1501 and the target domain 1503 .
[0788] As a sub-embodiment of this embodiment, when the first field 1502 is set to a first target value, the first MAC subheader consists of the first field 1502 , the LCID field 1501 and the target field 1503 .
[0789] As an embodiment, the target domain 1503 does not exist.
[0790] As a sub-embodiment of this embodiment, the first MAC subheader includes the first field 1502 and the LCID field 1501.
[0791] As a sub-embodiment of this embodiment, the first MAC subheader consists of the first field 1502 and the LCID field 1501.
[0792] As a sub-embodiment of this embodiment, when the first field 1502 is set to the second target value, the first MAC subheader consists of the first field 1502 and the LCID field 1501.
[0793] Example 16
[0794] Embodiment 16 illustrates a schematic diagram of a first MAC subheader according to the fifth embodiment of the present application, as shown in the attached Fig.16 As shown in the attached Fig.16 In the diagram, a box represents one or more domains.
[0795] In Embodiment 16, the first MAC subheader includes at least a first field 1602 , an LCID field 1601 , and an R field 1603 .
[0796] As an embodiment, the R domain 1603, the first domain 1602 and the LCID domain 1601 occupy the first byte (Oct 1), and the sum of the lengths of the R domain 1603, the first domain 1602 and the LCID domain 1601 is equal to one byte.
[0797] 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 load, and the second MAC load includes the first status report.
[0798] As a sub-embodiment of this embodiment, the second domain 1604 exists.
[0799] As a sub-embodiment of this embodiment, the first MAC subheader consists of the first field 1602 , the LCID field 1601 , the second field 1604 and the R field 1603 .
[0800] As a sub-embodiment of this embodiment, the length indicated by the second field 1604 includes the second MAC load field.
[0801] As a sub-embodiment of this embodiment, the length indicated by the second field 1604 does not include the second MAC load field.
[0802] As a sub-embodiment of this embodiment, the length of the second field is independent of the first field 1602.
[0803] As a sub-embodiment of this embodiment, the second field 1604 occupies the second byte (Oct 2), and the length of the second field 1604 is equal to one byte.
[0804] 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 load, and the second MAC load includes the first status report.
[0805] As a sub-embodiment of this embodiment, the second domain 1604 does not exist.
[0806] As a sub-embodiment of this embodiment, the first MAC subheader consists of the first field 1602 , the LCID field 1601 and the R field 1603 .
[0807] As an embodiment, the R domain 1603 is placed directly before the first domain 1602.
[0808] As an embodiment, the first domain 1602 is placed directly before the R domain 1603.
[0809] Embodiment 17
[0810] Embodiment 17 illustrates a schematic diagram of a first MAC subheader according to the sixth embodiment of the present application, as shown in the attached Fig.17 As shown in the attached Fig.17 In the diagram, a box represents one or more domains.
[0811] 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 includes a second MAC payload, and the second MAC payload includes the first status report.
[0812] As an embodiment, the first MAC subheader is composed of the first field 1704, the second field 1703, the first field 1702 and the LCID field 1701.
[0813] As an embodiment, the second domain 1703, the first domain 1702 and the LCID domain 1701 occupy the first byte (Oct 1), and the sum of the lengths of the second domain 1703, the first domain 1702 and the LCID domain 1701 is equal to one byte.
[0814] As an embodiment, the second field 1704 occupies the second byte (Oct 2), and the length of the second field 1704 is equal to one byte.
[0815] As an embodiment, the second domain 1703 and the second domain 1704 together constitute a domain.
[0816] As an embodiment, the second domain 1703 and the second domain 1704 are the same domain.
[0817] As an embodiment, the sum of the lengths of the second field 1703 and the second field 1704 is equal to 9 bits.
[0818] As an embodiment, the length indicated by the second field 1703 and the second field 1704 includes the second MAC load field.
[0819] As an embodiment, the length indicated by the second field 1703 and the second field 1704 does not include the second MAC load field.
[0820] Embodiment 18
[0821] Embodiment 18 illustrates a schematic diagram of a first MAC subheader according to the seventh embodiment of the present application, as shown in the attached Fig.18 As shown in the attached Fig.18 In the diagram, a box represents one or more domains.
[0822] In Example 18, the first MAC subheader includes an LCID domain 1801, an F domain 1802, a first domain 1803, a second domain 1804, a second domain 1805 and a target domain 1806; or the first MAC subheader includes an LCID domain 1801, an F domain 1802, a first domain 1803 and a second domain 1804; or the first MAC subheader includes an LCID domain 1801, an F domain 1802, a first domain 1803, a second domain 1804 and a second domain 1805; or the first MAC subheader includes an LCID domain 1801, an F domain 1802, a first domain 1803, a second domain 1804 and a target domain 1806.
[0823] As an embodiment, the target domain 1806 always exists.
[0824] As an embodiment, the target domain 1806 is optional.
[0825] As an example, the target domain 1806 exists.
[0826] As an embodiment, the target domain 1806 does not exist.
[0827] As an embodiment, the second domain 1805 is optional.
[0828] As an embodiment, the second domain 1805 exists.
[0829] As an embodiment, the second domain 1805 does not exist.
[0830] As an embodiment, both the target domain 1806 and the second domain 1805 exist.
[0831] As a sub-embodiment of this embodiment, the first status report belongs to the first MAC subheader.
[0832] 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.
[0833] 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 consists 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.
[0834] As an embodiment, neither the target domain 1806 nor the second domain 1805 exists.
[0835] As a sub-embodiment of this embodiment, the first status report belongs to the first MAC subheader.
[0836] As a sub-embodiment of this embodiment, the first MAC sub-PDU includes a second MAC payload, and the second MAC payload includes the first status report.
[0837] As a sub-embodiment of this embodiment, the first MAC subheader consists of the LCID field 1801, the F field 1802, the first field 1803 and the second field 1804.
[0838] 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 consists of the LCID field 1801, the F field 1802, the first field 1803 and the second field 1804.
[0839] As an embodiment, the target domain 1806 exists, and the second domain 1805 does not exist.
[0840] As a sub-embodiment of this embodiment, the first status report belongs to the first MAC subheader.
[0841] 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.
[0842] 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 consists of the LCID field 1801, the F field 1802, the first field 1803, the second field 1804 and the target field 1806.
[0843] As an embodiment, the target domain 1806 does not exist, and the second domain 1805 exists.
[0844] As a sub-embodiment of this embodiment, the first status report belongs to the first MAC subheader.
[0845] As a sub-embodiment of this embodiment, the first MAC sub-PDU includes a second MAC payload, and the second MAC payload includes the first status report.
[0846] As a sub-embodiment of this embodiment, the first MAC subheader consists of the LCID field 1801, the F field 1802, the first field 1803, the second field 1804 and the second field 1805.
[0847] 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 consists of the LCID field 1801, the F field 1802, the first field 1803, the second field 1804 and the second field 1805.
[0848] As an embodiment, the F field 1802, the first field 1803 and the LCID field 1801 occupy the first byte (Oct 1), and the sum of the lengths of the F field 1802, the first field 1803 and the LCID field 1801 is equal to one byte.
[0849] As an embodiment, when the second field 1805 exists, the second field 1805 occupies the third byte (Oct 3), and the length of the second field 1805 is equal to 1 byte.
[0850] As an embodiment, when the second field 1805 exists, the second field 1804 and the second field 1805 occupy the second byte (Oct 2) and the 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.
[0851] As an embodiment, when the target domain 1806 exists, the target domain 1806 occupies the third byte (Oct 3) or the fourth byte (Oct 4), and the length of the target domain 1806 is equal to one byte.
[0852] Embodiment 19
[0853] Embodiment 19 illustrates a schematic diagram of a first MAC subheader according to the eighth embodiment of the present application, as shown in the attached Fig.19 As shown in the attached Fig.19 In the diagram, a box represents one or more domains.
[0854] 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 includes a second MAC payload, and the second MAC payload includes the first status report. .
[0855] As an embodiment, the first MAC subheader is composed of the second field 1903, the first field 1902 and the LCID field 1901.
[0856] As an embodiment, the first domain 1902 and the LCID domain 1901 occupy the first byte (Oct 1), and the sum of the lengths of the first domain 1902 and the LCID domain 1901 is equal to one byte; the second domain 1903 occupies the second byte (Oct 2).
[0857] As an embodiment, the length of the first field 1902 is equal to 2 bits.
[0858] Embodiment 20
[0859] 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 the attached figure. Fig. 20 As shown in the attached Fig. 20 In the diagram, a box represents one or more domains.
[0860] In embodiment 20, the first MAC sub-PDU includes a first MAC load field 2002 and a second MAC load field 2001, the second MAC load field 2001 is placed directly before the first MAC load field 2002, the first MAC load field 2002 includes the first MAC load, the second MAC load field 2001 includes the second MAC load, and the second MAC load includes the first status report.
[0861] As an embodiment, the second MAC load domain 2001 always exists.
[0862] As an embodiment, the second MAC load domain 2001 is optional.
[0863] As a sub-embodiment of this embodiment, when the first field in the first MAC subheader is used to indicate that the first MAC sub-PDU includes the first status report, the second MAC payload field 2001 exists.
[0864] As a sub-embodiment of this embodiment, when the first field in the first MAC subheader is used to indicate that the first MAC sub-PDU does not include the first status report, the second MAC load field 2001 does not exist.
[0865] Embodiment 21
[0866] 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 the attached figure. Fig.21 As shown in the attached Fig.21 In the diagram, a box represents one or more domains.
[0867] In embodiment 21, the first MAC sub-PDU includes a first MAC load field 2101 and a second MAC load field 2102, the second MAC load field 2102 is placed directly before the first MAC load field 2101, the first MAC load field 2101 includes the first MAC load, the second MAC load field 2102 includes the second MAC load, and the second MAC load includes the first status report.
[0868] As an embodiment, the second MAC load domain 2102 always exists.
[0869] As an embodiment, the second MAC load domain 2102 is optional.
[0870] As a sub-embodiment of this embodiment, when the first field in the first MAC subheader is used to indicate that the first MAC sub-PDU includes the first status report, the second MAC payload field 2102 exists.
[0871] As a sub-embodiment of this embodiment, when the first field in the first MAC subheader is used to indicate that the first MAC sub-PDU does not include the first status report, the second MAC payload field 2102 does not exist.
[0872] Embodiment 22
[0873] Embodiment 22 illustrates a structural block diagram of a processing device used in a first node according to an embodiment of the present application; Fig. 22 As shown in the attached Fig. 22 In the embodiment, the processing device 2200 in the first node includes a first receiver 2201 and a first transmitter 2202.
[0874] The first transmitter 2202 constructs a first MAC PDU; sends the first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load;
[0875] In Embodiment 22, the first field is a field in the first MAC subheader other than the LCID field; and the first MAC payload is not the first status report.
[0876] As an embodiment, the first status report belongs to the first MAC subheader.
[0877] As an embodiment, the first MAC sub-PDU includes a second MAC payload, and the second MAC payload includes the first status report.
[0878] As an embodiment, the first MAC subheader includes a second field, and the second field indicates the length of the first MAC payload.
[0879] As an embodiment, the first transmitter 2202 sends a first message; along with the first message, at least the first DRB is restored; as a response to the first condition set being met, the first status report is triggered; wherein the first message is used for the first RRC recovery process; the first condition set includes that the first RRC recovery process is being executed, and the first data block is effective, and the first data block is associated with the first DRB; the first status report indicates a cache-related status.
[0880] As an embodiment, the first receiver 2201 receives first signaling, where 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.
[0881] As an embodiment, the first receiver 2201 includes the attached Figure 4 Antenna 452, receiver 454, multi-antenna reception processor 458, reception processor 456, controller / processor 459, memory 460 and data source 467.
[0882] As an embodiment, the first receiver 2201 includes the attached Figure 4 Antenna 452, receiver 454, multi-antenna receive processor 458, and receive processor 456.
[0883] As an embodiment, the first receiver 2201 includes the attached Figure 4 Antenna 452, receiver 454, and receive processor 456.
[0884] As an embodiment, the first transmitter 2202 includes the attached Figure 4 Antenna 452, transmitter 454, multi-antenna transmit processor 457, transmit processor 468, controller / processor 459, memory 460 and data source 467.
[0885] As an embodiment, the first transmitter 2202 includes the attached Figure 4 Antenna 452, transmitter 454, multi-antenna transmit processor 457, and transmit processor 468.
[0886] As an embodiment, the first transmitter 2202 includes the attached Figure 4 Antenna 452, transmitter 454, and transmit processor 468.
[0887] Embodiment 23
[0888] Embodiment 23 illustrates a structural block diagram of a processing device used in a second node according to an embodiment of the present application; Fig.23 As shown in the attached Fig.23 In the embodiment, the processing device 2300 in the second node includes a second transmitter 2301 and a second receiver 2302.
[0889] The second receiver 2302 receives a first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load;
[0890] In Example 23, the first MAC PDU is constructed; the first field is a field in the first MAC subheader other than the LCID field; and the first MAC payload is not the first status report.
[0891] As an embodiment, the first status report belongs to the first MAC subheader.
[0892] As an embodiment, the first MAC sub-PDU includes a second MAC payload, and the second MAC payload includes the first status report.
[0893] As an embodiment, the first MAC subheader includes a second field, and the second field indicates the length of the first MAC payload.
[0894] As an embodiment, the second receiver 2302 receives a first message; wherein, along with the first message, at least the first DRB is restored; as a response to the first condition set being satisfied, the first status report is triggered; the first message is used for a first RRC recovery process; the first condition set includes that the first RRC recovery process is being executed, and a first data block is effective, and the first data block is associated with the first DRB; the first status report indicates a cache-related status.
[0895] As an embodiment, the second transmitter 2301 sends a first signaling, wherein 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.
[0896] As an embodiment, the second transmitter 2301 includes the attached Figure 4 Antenna 420, transmitter 418, multi-antenna transmit processor 471, transmit processor 416, controller / processor 475, and memory 476.
[0897] As an embodiment, the second transmitter 2301 includes the attached Figure 4 Antenna 420, transmitter 418, multi-antenna transmit processor 471, and transmit processor 416.
[0898] As an embodiment, the second transmitter 2301 includes the attached Figure 4 Antenna 420, transmitter 418, and transmit processor 416.
[0899] As an embodiment, the second receiver 2302 includes the attached Figure 4 Antenna 420, receiver 418, multi-antenna reception processor 472, reception processor 470, controller / processor 475, and memory 476.
[0900] As an embodiment, the second receiver 2302 includes the attached Figure 4 Antenna 420, receiver 418, multi-antenna receive processor 472, receive processor 470.
[0901] As an embodiment, the second receiver 2302 includes the attached Figure 4 Antenna 420, receiver 418, and receive processor 470.
[0902] Embodiment 24
[0903] Embodiment 24 illustrates a schematic diagram of a target domain or a second MAC load domain according to an embodiment of the present application, as shown in the attached Fig.24 As shown in the attached Fig.24 In the figure, a box represents one domain or multiple domains; the sum of the lengths of the first status report domain 2402 and the other domains 2401 is equal to 1 byte.
[0904] 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.
[0905] As an embodiment, the other field 2401 is placed directly before the first status report field 2402.
[0906] As an embodiment, the other field 2401 is placed directly after the first status report field 2402.
[0907] In Embodiment 24, the first status report field is used to indicate the first status report, the length of the first status report field is equal to L1 bits, and the L1 is not greater than the L0.
[0908] As an embodiment, the first status reporting domain 2402 is a MAC domain.
[0909] As an embodiment, the L1 is equal to the L0.
[0910] As an embodiment, the L1 is smaller than the L0.
[0911] As an embodiment, L1 is equal to 8.
[0912] As an embodiment, L1 is equal to 7.
[0913] As an embodiment, L1 is equal to 6.
[0914] As an embodiment, L1 is equal to 5.
[0915] As an embodiment, L1 is equal to 4.
[0916] As an embodiment, L1 is equal to 3.
[0917] As an embodiment, L1 is equal to 2.
[0918] As an embodiment, L1 is equal to 1.
[0919] As an embodiment, the attached Fig.24 is the target domain.
[0920] As a subsidiary embodiment of this sub-embodiment, the first status report domain is a domain in the target domain.
[0921] As a subsidiary embodiment of this sub-embodiment, the target domain is composed of the first status report domain 2402 and the other domains 2401.
[0922] As a subsidiary embodiment of this sub-embodiment, the target domain does not include other domains 2401.
[0923] As a subordinate embodiment of this subsidiary embodiment, the target domain is composed of the first status report domain 2402.
[0924] As a subordinate embodiment of this subsidiary embodiment, the target domain includes only one MAC domain.
[0925] As a subsidiary embodiment of this sub-embodiment, the target domain includes other domains 2401 , and the other domains 2401 are different from the first status report domain 2402 .
[0926] As a subordinate embodiment of this subsidiary 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.
[0927] As a subordinate embodiment of this subsidiary embodiment, the target domain is composed of the first status report domain 2402 and the other domains 2401.
[0928] As a subordinate embodiment of this subsidiary embodiment, the first status report field 2402 and the other field 2401 are used to indicate the uplink data amount and the power margin respectively.
[0929] As a subordinate embodiment of this subsidiary embodiment, the first status report field 2402 and the other fields 2401 are respectively used to indicate the uplink data volume and listen-before-speak failure.
[0930] As a subordinate embodiment of this subsidiary embodiment, the first status report field 2402 and the other field 2401 are used to indicate the uplink data volume and beam failure, respectively.
[0931] As a subordinate embodiment of this subsidiary embodiment, the first status report field 2402 is used to indicate the amount of uplink data, and the other field 2401 is an R field.
[0932] As a subordinate embodiment of this subsidiary embodiment, the other domains 2401 include the R domain.
[0933] As a subordinate embodiment of this subsidiary embodiment, the other domains 2401 include at least one MAC domain.
[0934] As an embodiment, the attached Fig.24 It is the second MAC load domain.
[0935] As a subsidiary embodiment of this sub-embodiment, the first status report field is a field in the second MAC load field.
[0936] As a subsidiary embodiment of this sub-embodiment, the second MAC load domain is composed of the first status report domain 2402 and the other domain 2401.
[0937] As a subsidiary embodiment of this sub-embodiment, the second MAC load domain does not include other domains 2401.
[0938] As a subordinate embodiment of this subsidiary embodiment, the second MAC load field is composed of the first status report field 2402.
[0939] As a subordinate embodiment of this subsidiary embodiment, the second MAC load domain includes only one MAC domain.
[0940] As a subsidiary embodiment of this sub-embodiment, the second MAC load domain includes other domains 2401, and the other domains 2401 are different from the first status report domain 2402.
[0941] As a subordinate embodiment of this subsidiary embodiment, the length of the other field 2401 is equal to the difference between the length of the second MAC load field and the length of the first status report field 2402.
[0942] As a subordinate embodiment of this subsidiary embodiment, the second MAC load domain is composed of the first status report domain 2402 and the other domain 2401.
[0943] As a subordinate embodiment of this subsidiary embodiment, the first status report field 2402 and the other field 2401 are used to indicate the uplink data amount and the power margin respectively.
[0944] As a subordinate embodiment of this subsidiary embodiment, the first status report field 2402 and the other fields 2401 are respectively used to indicate the uplink data volume and listen-before-speak failure.
[0945] As a subordinate embodiment of this subsidiary embodiment, the first status report field 2402 and the other field 2401 are used to indicate the uplink data volume and beam failure, respectively.
[0946] As a subordinate embodiment of this subsidiary embodiment, the first status report field 2402 and the other fields 2401 are used to indicate the uplink data volume and the R field respectively.
[0947] As a subordinate embodiment of this subsidiary embodiment, the other domains 2401 include the R domain.
[0948] As a subordinate embodiment of this subsidiary embodiment, the other domains 2401 include at least one MAC domain.
[0949] As an embodiment, the target domain and the second MAC load domain do not exist at the same time.
[0950] As an embodiment, the target domain exists and the second MAC load domain does not exist.
[0951] As an embodiment, the target domain does not exist, and the second MAC load domain exists.
[0952] A person of ordinary skill in the art can understand that all or part of the steps in the above method can be completed by instructing the relevant hardware through a program, and the program can be stored in a computer-readable storage medium, such as a read-only memory, a hard disk or an optical disk. Optionally, all or part of the steps in the above embodiment can also be implemented using one or more integrated circuits. Accordingly, each module unit in the above embodiment can be implemented in the form of hardware or in the form of a software function module, and the present application is not limited to any specific form of software and hardware combination. The user equipment, terminal and UE in the present application include but are not limited to drones, communication modules on drones, remote-controlled aircraft, aircraft, small aircraft, mobile phones, tablet computers, notebooks, vehicle-mounted communication equipment, wireless sensors, Internet cards, Internet of Things terminals, RFID terminals, NB-IOT terminals, MTC (Machine Type Communication, Machine Type Communication) terminals, eMTC (enhanced MTC, enhanced MTC) terminals, data cards, Internet cards, vehicle-mounted communication equipment, low-cost mobile phones, low-cost tablet computers and other wireless communication devices. The base stations or system devices in this application include but are not limited to macrocell base stations, microcell base stations, home base stations, relay base stations, gNB (NR Node B) NR Node B, TRP (Transmitter Receiver Point) and other wireless communication devices.
[0953] The above is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. 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 used for wireless communication, characterized in that: include: A first receiver receives a first signaling; A first transmitter, forming a first MAC PDU; Sending the first MAC PDU; The first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC payload; The first field is a field in the first MAC subheader other than the LCID field; the first MAC payload is not the first status report; 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; and the first signaling includes a field in an RRC message.
2. The first node according to claim 1, characterized in that: The first status report belongs to the first MAC subheader; the first status report is used to provide the uplink data volume of the MAC entity.
3. The first node according to claim 1, characterized in that: The first MAC sub-PDU includes a second MAC payload, and the second MAC payload includes the first status report.
4. The first node according to any one of claims 1 to 3, characterized in that: The first MAC subheader includes a second field, and the second field indicates the length of the first MAC payload.
5. The first node according to any one of claims 1 to 4, characterized in that: include: The first transmitter sends a first message; Along with the first message, recover at least a first DRB; In response to the first set of conditions being met, triggering the first status report; Among them, the first message is used for the first RRC recovery process; the first condition set includes that the first RRC recovery process is being executed, and the first data block is effective, and the first data block is associated with the first DRB; the first status report indicates the cache-related status.
6. The first node according to any one of claims 1 to 5, characterized in that: The one RRC message includes SIB1, or, The one RRC message includes RRCReconfiguration or RRCConnectionReconfiguration.
7. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first signaling; A second receiver receives a first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load; wherein the first MAC PDU is formed; the first field is a field in the first MAC subheader other than the LCID field; the first MAC payload is not the first status report; 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; the first signaling includes a field in an RRC message.
8. The second node according to claim 7, characterized in that: The first status report belongs to the first MAC subheader; the first status report is used to provide the uplink data volume of the MAC entity.
9. The second node according to claim 7 or 8, characterized in that: The first MAC sub-PDU includes a second MAC payload, and the second MAC payload includes the first status report.
10. The second node according to any one of claims 7 to 9, characterized in that: The first MAC subheader includes a second field, and the second field indicates the length of the first MAC payload.
11. The second node according to any one of claims 7 to 10, characterized in that: The second receiver receives a first message; wherein, along with the first message, at least the first DRB is restored; as a response to the first condition set being satisfied, the first status report is triggered; the first message is used for a first RRC recovery process; the first condition set includes that the first RRC recovery process is being executed and a first data block is effective, and the first data block is associated with the first DRB; the first status report indicates a cache-related status.
12. The second node according to any one of claims 7 to 11, characterized in that: The one RRC message includes SIB1, or, The one RRC message includes RRCReconfiguration or RRCConnectionReconfiguration.
13. A method in a first node for wireless communication, characterized in that: include: receiving a first signaling; Building the first MAC PDU; Sending the first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load; The first field is a field in the first MAC subheader other than the LCID field; the first MAC payload is not the first status report; 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; and the first signaling includes a field in an RRC message.
14. The method in the first node according to claim 13, characterized in that: The first status report belongs to the first MAC subheader; the first status report is used to provide the uplink data volume of the MAC entity.
15. The method in the first node according to claim 13 or 14, characterized in that: The first MAC sub-PDU includes a second MAC payload, and the second MAC payload includes the first status report.
16. The method in the first node according to any one of claims 13 to 15, characterized in that: The first MAC subheader includes a second field, and the second field indicates the length of the first MAC payload.
17. The method in the first node according to any one of claims 13 to 16, characterized in that: include: Sending a first message; restoring at least a first DRB (Data Radio Bearer) along with the first message; triggering the first status report in response to the first set of conditions being met; Among them, the first message is used for the first RRC (Radio Resource Control) recovery process; the first condition set includes that the first RRC recovery process is being executed, and the first data block is effective, and the first data block is associated with the first DRB; the first status report indicates the cache-related status.
18. The method in the first node according to any one of claims 13 to 17, characterized in that: The one RRC message includes SIB1, or, The one RRC message includes RRCReconfiguration or RRCConnectionReconfiguration.
19. A method in a second node for wireless communication, characterized in that: include: Sending a first signaling; Receive a first MAC PDU; the first MAC PDU includes a first MAC sub-PDU, the first MAC sub-PDU includes a first MAC sub-header, the first MAC sub-header includes at least a first field and an LCID field, the first field in the first MAC sub-header is used to indicate whether the first MAC sub-PDU includes a first status report, and the LCID field of the first MAC sub-PDU is used to indicate a first MAC load; wherein the first MAC PDU is formed; the first field is a field in the first MAC subheader other than the LCID field; the first MAC payload is not the first status report; 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; the first signaling includes a field in an RRC message.
20. The method in the second node according to claim 19, characterized in that: The first status report belongs to the first MAC subheader; the first status report is used to provide the uplink data volume of the MAC entity.
21. The method in the second node according to claim 19 or 20, characterized in that: The first MAC sub-PDU includes a second MAC payload, and the second MAC payload includes the first status report.
22. The method in the second node according to any one of claims 19 to 21, characterized in that: The first MAC subheader includes a second field, and the second field indicates the length of the first MAC payload.
23. The method in the second node according to any one of claims 19 to 22, characterized in that: include: receiving a first message; Wherein, along with the first message, at least the first DRB is restored; The first status report is triggered in response to a first set of conditions being met; the first message is used for a first RRC recovery process; the first set of conditions includes that the first RRC recovery process is being executed and a first data block is effective, and the first data block is associated with the first DRB; the first status report indicates a cache-related status.
24. The method in the second node according to any one of claims 19 to 23, characterized in that: The one RRC message includes SIB1, or, The one RRC message includes RRCReconfiguration or RRCConnectionReconfiguration.
