A method and apparatus for use in a communication node for wireless communication

Abstract

This application discloses a method and apparatus for use in a communication node for wireless communication. The communication node receives a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicating a first logical identifier, the first logical identifier being configured and associated with a first bearer; in response to the reception of the first MAC PDU, the first MAC subPDU is discarded; the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a secondary link; or, the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI. This application avoids accepting erroneous MAC subPDUs.

Description

A method and apparatus for use in a communication node for wireless communication

[0001] This application claims priority to the Chinese patent application filed with the China Patent Office on March 22, 2024, with application number 202410338862.9 and application name “A method and device in a communication node used for wireless communication”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to a transmission method and apparatus in a wireless communication system, and in particular to a MAC PDU processing method and apparatus. Background Art

[0003] When a user equipment (UE) receives a MAC (Medium Access Control) PDU (Protocol Data Unit), section 5.13 of 3GPP (the 3rd Generation Partnership Project) TS38.321 specifies that the MAC entity should discard unknown, unforeseen and erroneous protocol data, and specifically defines the conditions that unknown, unforeseen and erroneous protocol data must meet.

[0004] 3GPP Rel-17 launched a work item (WI) on receiving MBS (Multicast / Broadcast Service) in the RRC connected state and completed the standardization work. To reduce power consumption, reduce signaling overhead and shorten latency, Rel-18 established the "Enhancements of NR Multicast and Broadcast Services" work item to support MBS reception in the RRC inactive state.

[0005] 3GPP RAN approved a study item in Rel-17, "NR Sidelink Relay Study," to cover the enhancements and solutions needed to support UE-to-network relay and UE-to-UE relay coverage extension, while considering a wider range of V2X, public safety, and commercial applications and services. Rel-18 supports multipath relay, where remote terminals connect to the network via direct and indirect paths to improve reliability / robustness and throughput. Summary of the Invention

[0006] The inventors have discovered through research that, as communication scenarios become more complex, existing protocols have at least one of the following problems:

[0007] -. The existing protocol does not consider the case where the RB associated with the multicast data received in RRC_INACTIVE is suspended;

[0008] -. The existing protocol does not consider the case where the RB associated with the unicast data received via the sidelink (DL) is suspended;

[0009] -. The existing protocol does not consider the situation where the configured LCID (Logical Channel ID) or eLCID (Extended Logical Channel ID) associated with the received multicast data is not associated with the G (Group)-RNTI (Radio Network Temporary Identity) or G-CS-RNTI (Group Configured Scheduling RNTI) for this multicast data.

[0010] When the above situation occurs, the UE may receive unknown, unpredictable and erroneous protocol data, which may affect the UE.

[0011] To address the above issues, this application provides a solution for processing MAC PDUs. While the NR system is used as an example in the description of the above issues, this application is also applicable to scenarios such as LTE (Long-Term Evolution), LTE-A (Long-Term Evolution Advanced), or future 5G+ or 6G systems, achieving technical effects similar to those of the NR system. Furthermore, adopting a unified design solution for different scenarios also helps reduce hardware complexity and cost. Furthermore, although this application provides a specific implementation for RRC_INACTIVE MBS, this application can also be used in RRC_IDLE MBS scenarios, achieving technical effects similar to those of RRC_INACTIVE MBS. Furthermore, although this application is initially intended for the Uu air interface, this application can also be used for the PC5 interface, achieving technical effects similar to those of the Uu air interface. Furthermore, although this application is initially intended for terrestrial network (TN) scenarios, this application is also applicable to non-terrestrial network (NTN) communication scenarios, achieving technical effects similar to those in TN scenarios. In addition, adopting a unified solution for different scenarios can also help reduce hardware complexity and costs.

[0012] As an embodiment, the interpretation of terminology in this application refers to the definition of 3GPP specification protocol TS36 series.

[0013] As an embodiment, the interpretation of the terms in this application refers to the definition of the 3GPP specification protocol TS38 series.

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

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

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

[0017] Receive a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer;

[0018] In response to receiving the first MAC PDU, discarding the first MAC subPDU;

[0019] wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link;

[0020] or,

[0021] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0022] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via SL-SCH (Sidelink Shared Channel).

[0023] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast and the first MAC PDU is received via SL-SCH.

[0024] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast.

[0025] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast and the first MAC PDU is for MBS.

[0026] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via SL-SCH.

[0027] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via unicast and the first MAC PDU is received via SL-SCH.

[0028] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being associated with a G-RNTI other than the first G-RNTI, wherein the first MAC PDU is identified by the first G-RNTI.

[0029] The problem to be solved by this application includes: how to process the first MAC subPDU.

[0030] The problems to be solved by this application include: when the first MAC subPDU in the first MAC PDU received via non-unicast indicates a first logical identifier and the first logical identifier is configured and the first logical identifier is associated with a first bearer, if the first bearer is suspended, how to process the first MAC subPDU.

[0031] The problems to be solved by this application include: when the first MAC subPDU in the first MAC PDU received via non-unicast indicates a first logical identifier and the first logical identifier is configured and the first logical identifier is associated with a first bearer, if the first bearer is associated with a G-RNTI other than the first G-RNTI, how to process the first MAC subPDU.

[0032] The above method solves the above problem by discarding the first MAC subPDU.

[0033] The above method regards the first MAC subPDU as an erroneous MAC subPDU.

[0034] The above method avoids executing the first MAC subPDU.

[0035] The above method avoids executing an erroneous MAC subPDU.

[0036] According to one aspect of the present application, it is characterized in that the first RNTI is G-RNTI; the non-unicast is multicast; and the first MAC PDU is received through the first RNTI.

[0037] The problem to be solved by this application includes: how to process the first MAC subPDU when the first MAC PDU is identified by a G-RNTI and the non-unicast is multicast.

[0038] The problems to be solved by this application include: when the first MAC subPDU in the first MAC PDU identified by G-RNTI received via multicast indicates a first logical identifier and the first logical identifier is configured and the first logical identifier is associated with a first bearer, if the first bearer is suspended, how to handle the first MAC subPDU.

[0039] The above method solves the above problem by discarding the first MAC subPDU.

[0040] The above method regards the first MAC subPDU as an erroneous MAC subPDU.

[0041] The above method avoids executing the first MAC subPDU.

[0042] The above method avoids executing an erroneous MAC subPDU.

[0043] According to one aspect of the present application, it is characterized in that the first logical identifier is unicast; and the first MAC PDU is received through a secondary link.

[0044] According to one aspect of the present application, it is characterized in that the first MAC PDU is for MBS; the non-unicast is multicast; and the first MAC PDU is received via non-unicast.

[0045] The problem to be solved by the present application includes: how to process the first MAC subPDU when the first MAC PDU is identified by the RNTI for the secondary link and is received via unicast.

[0046] The problems to be solved by this application include: when the first MAC subPDU in the first MAC PDU identified by the RNTI of the secondary link received via unicast indicates a first logical identifier and the first logical identifier is configured and the first logical identifier is associated with a first bearer, if the first bearer is suspended, how to handle the first MAC subPDU.

[0047] The above method solves the above problem by discarding the first MAC subPDU.

[0048] The above method regards the first MAC subPDU as an erroneous MAC subPDU.

[0049] The above method avoids executing the first MAC subPDU.

[0050] The above method avoids executing an erroneous MAC subPDU.

[0051] According to one aspect of the present application, it is characterized by comprising:

[0052] receiving a first RRC message; and in response to receiving the first RRC message, maintaining an RRC_INACTIVE state and suspending the first bearer;

[0053] The first RRC message indicates that data is transmitted through at least one bearer in the RRC_INACTIVE state; and the first bearer is a bearer other than the at least one bearer.

[0054] The problem to be solved by the present application includes: how to process the first MAC subPDU when the first bearer is not the bearer indicated by the first RRC message to transmit data in the RRC_INACTIVE state.

[0055] The problem to be solved by this application includes: how to suspend the first bearer.

[0056] The above method solves the above problem by receiving the first RRC message indicating that data is transmitted through at least one bearer in the RRC_INACTIVE state, triggering the maintenance of the RRC_INACTIVE state and suspending the first bearer.

[0057] According to one aspect of the present application, it is characterized by comprising:

[0058] Determining that a connection failure occurs; and suspending the first bearer in response to the determination that the connection failure occurs.

[0059] The problem to be solved by this application includes: how to suspend the first bearer.

[0060] The above method solves the above problem by determining that a connection failure occurs to trigger the suspension of the first bearer.

[0061] The present application discloses a method used in a second node of wireless communication, characterized by comprising:

[0062] Sending a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in response to receiving the first MAC PDU, the receiver of the first MAC PDU discards the first MAC subPDU;

[0063] wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link;

[0064] or,

[0065] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0066] According to one aspect of the present application, it is characterized in that the first RNTI is G-RNTI; the non-unicast is multicast; and the first MAC PDU is received through the first RNTI.

[0067] According to one aspect of the present application, it is characterized in that the first logical identifier is unicast; and the first MAC PDU is received through a secondary link.

[0068] According to one aspect of the present application, it is characterized in that the first MAC PDU is for MBS; the non-unicast is multicast; and the first MAC PDU is received via non-unicast.

[0069] According to one aspect of the present application, it is characterized by comprising:

[0070] Sending a first RRC message;

[0071] In which, as a response to the receipt of the first RRC message, the recipient of the first MAC PDU maintains the RRC_INACTIVE state and suspends the first bearer; the first RRC message indicates that data is transmitted through at least one bearer in the RRC_INACTIVE state; and the first bearer is a bearer other than the at least one bearer.

[0072] According to one aspect of the present application, it is characterized in that the receiver of the first MAC PDU determines that a connection failure occurs; in response to the determination of the connection failure, the receiver of the first MAC PDU suspends the first bearer.

[0073] The present application discloses a first node used for wireless communication, characterized by comprising:

[0074] A first receiver receives a first MAC PDU, wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer;

[0075] a first transmitter, in response to receiving the first MAC PDU, discarding the first MAC subPDU;

[0076] wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link;

[0077] or,

[0078] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0079] The present application discloses a second node used for wireless communication, characterized by comprising:

[0080] A second transmitter sends a first MAC PDU, wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in response to receiving the first MAC PDU, a receiver of the first MAC PDU discards the first MAC subPDU;

[0081] wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link;

[0082] or,

[0083] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0085] FIG1 shows a flow chart of transmission of a first MAC PDU according to an embodiment of the present application;

[0086] FIG2 shows a schematic diagram of a network architecture according to an embodiment of the present application;

[0087] FIG3 is a schematic diagram showing an embodiment of a radio protocol architecture of a user plane and a control plane according to an embodiment of the present application;

[0088] FIG4 shows a schematic diagram of a first communication device and a second communication device according to an embodiment of the present application;

[0089] FIG5 shows a wireless signal transmission flow chart according to an embodiment of the present application;

[0090] FIG6 shows a wireless signal transmission flow chart according to another embodiment of the present application;

[0091] FIG7 shows a wireless signal transmission flow chart according to yet another embodiment of the present application;

[0092] FIG8 shows a flowchart of suspending a first bearer according to an embodiment of the present application;

[0093] FIG9 shows a flowchart of suspending a first bearer according to yet another embodiment of an embodiment of the present application;

[0094] FIG10 shows a structural block diagram of a processing device used in a first node according to an embodiment of the present application;

[0095] FIG11 shows a structural block diagram of a processing device used in a second node according to an embodiment of the present application. DETAILED DESCRIPTION

[0096] 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 and features in the embodiments of the present application can be combined with each other in any way.

[0097] Example 1

[0098] 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 FIG1. ​​In FIG1, each box represents a step, and it is particularly important to emphasize that the order of the boxes in the figure does not represent the temporal sequence between the steps represented.

[0099] In embodiment 1, the first node in the present application receives a first MAC PDU in step 101; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in step 102, as a response to receiving the first MAC PDU, the first MAC subPDU is discarded;

[0100] wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link;

[0101] or,

[0102] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0103] As an embodiment, the first MAC PDU for the first RNTI means that: the first MAC PDU is received through the first RNTI.

[0104] As an embodiment, the first MAC PDU for the first RNTI means that the first MAC PDU is identified by the first RNTI.

[0105] As an embodiment, the first MAC PDU for the first RNTI means that a CRC (Cyclic Redundancy Check) of a TB (Transmission Block) corresponding to the first MAC PDU is scrambled by the first RNTI.

[0106] As an embodiment, the first MAC PDU for the first RNTI means that the CRC of the DCI (Downlink Control Information) that schedules the first MAC PDU is scrambled by the first RNTI.

[0107] As an embodiment, the first RNTI is an RNTI.

[0108] As an embodiment, the first RNTI is a bit string (BIT string).

[0109] As an embodiment, the first RNTI is a sixteen-bit bit string.

[0110] As an embodiment, the first RNTI is a hexadecimal value.

[0111] As an embodiment, the value of the first RNTI is not less than 0001 (hexadecimal) and not greater than FFF2 (hexadecimal).

[0112] As an embodiment, the first RNTI is of the first MAC entity.

[0113] As an embodiment, the first RNTI is for the first MAC entity.

[0114] As an embodiment, the first MAC entity receives the first MAC PDU.

[0115] As an embodiment, the first MAC entity is a MAC entity corresponding to the secondary link.

[0116] As an embodiment, the first MAC entity is a MAC entity corresponding to MCG (Master Cell Group).

[0117] As an embodiment, the first MAC entity is a MAC entity corresponding to SCG (Secondary Cell Group).

[0118] As an embodiment, the definition of MAC PDU in this application refers to the MAC PDU in Section 6 of 3GPP TS 38.321.

[0119] As an embodiment, the resources occupied by the first MAC PDU are dynamically scheduled.

[0120] As an embodiment, the resources occupied by the first MAC PDU are configured by RRC.

[0121] As an embodiment, the resources occupied by the first MAC PDU are configured by RRC and activated by DCI.

[0122] As an embodiment, the resources occupied by the first MAC PDU are configured downlink assignments.

[0123] As an embodiment, the first MAC PDU is for a secondary link.

[0124] As an embodiment, the first MAC PDU is received through PSSCH (Physical Sidelink Shared Channel).

[0125] As an embodiment, the first MAC PDU is received via SL-SCH (Sidelink Shared Channel).

[0126] As an embodiment, the first MAC PDU is a SL MAC PDU.

[0127] As an embodiment, the first MAC PDU is downlink (DL).

[0128] As an embodiment, the first MAC PDU is received via PDSCH (Physical Downlink Shared Channel).

[0129] As an embodiment, the first MAC PDU is received via DL-SCH (Downlink Shared Channel).

[0130] As an embodiment, the first MAC PDU is a DL MAC PDU.

[0131] As an embodiment, the definition of MAC subPDU in this application refers to the MAC subPDU in Section 6 of 3GPP TS 38.321.

[0132] As an embodiment, the first MAC PDU is composed of a positive integer number of MAC subPDUs.

[0133] As an embodiment, the first MAC PDU consists of a MAC subPDU.

[0134] As an embodiment, the first MAC PDU is composed of multiple MAC subPDUs.

[0135] As an embodiment, the first MAC PDU includes a padding MAC SDU.

[0136] As an embodiment, the first MAC PDU does not include a padding MAC SDU.

[0137] As an embodiment, the first MAC PDU includes padding MAC CE.

[0138] As an embodiment, the first MAC PDU does not include padding MAC CE.

[0139] As an embodiment, the first MAC subPDU consists of a MAC SDU, and the one MAC SDU indicates the first logical identifier.

[0140] As an embodiment, the first MAC subPDU consists of a MAC SDU and a MAC subheader.

[0141] As an embodiment, the MAC subheader in the first MAC subPDU indicates the first logical identifier.

[0142] As an embodiment, a field in the MAC subheader in the first MAC subPDU indicates the first logical identifier.

[0143] As an embodiment, the MAC subheader in the first MAC subPDU includes an LCID field, and the LCID field indicates the first logical identifier.

[0144] As an embodiment, the MAC subheader in the first MAC subPDU includes an eLCID field, and the eLCID field indicates the first logical identifier.

[0145] As an embodiment, the MAC subheader in the first MAC subPDU includes an LCID field and an eLCID field, and the LCID field and the eLCID field indicate the first logical identifier.

[0146] As an embodiment, the first logical identifier is an identifier of a logical channel.

[0147] As an embodiment, the first logical identifier indicates a logical channel.

[0148] As an embodiment, the first logical identifier is a LogicalChannelIdentity.

[0149] As an embodiment, the first logical identifier corresponds to an LCID.

[0150] As an embodiment, the first logical identifier corresponds to an eLCID.

[0151] As an embodiment, the first logical identifier corresponds to either an LCID or an eLCID.

[0152] As an embodiment, the first logical identifier is configured by an RRC signaling.

[0153] As an embodiment, the first logical identity is configured by a domain whose name includes LogicalChannelIdentity.

[0154] As an embodiment, the first logical identifier is configured by a LogicalChannelIdentity.

[0155] As an embodiment, the first logical identifier is configured by a LogicalChannelIdentityExt.

[0156] As an embodiment, the first logical identifier is associated with the first bearer by an RRC signaling configuration.

[0157] As an embodiment, the first bearer corresponds to a PDCP entity.

[0158] As an embodiment, the first bearer corresponds to multiple PDCP entities.

[0159] As an embodiment, the first bearer corresponds to an RLC entity.

[0160] As an embodiment, the first bearer corresponds to multiple RLC entities.

[0161] As an embodiment, the first bearer is used to carry service data.

[0162] As an embodiment, the first bearer is used to carry control signaling.

[0163] As an embodiment, the first bearer is a wireless bearer.

[0164] As an embodiment, the first bearer is a Uu wireless bearer.

[0165] As an embodiment, the first bearer is a wireless bearer of NR Uu.

[0166] As an embodiment, the first bearer is an SRB (Signalling Radio Bearer).

[0167] As an embodiment, the first bearer is a DRB ((user) Data Radio Bearer).

[0168] As an embodiment, the first bearer is configured by a domain whose name includes pdcp-Config.

[0169] As an embodiment, the first bearer is configured by a pdcp-Config.

[0170] As an embodiment, the first bearer is configured by a RadioBearerConfig field.

[0171] As an embodiment, the first bearer is configured by a DRB-Identity.

[0172] As an embodiment, the first logical identifier being associated with the first bearer means that the first logical identifier is configured for the first bearer.

[0173] As an embodiment, the first logical identifier being associated with the first bearer means that the first bearer is configured for the first logical identifier.

[0174] As an embodiment, the first logical identifier being associated with the first bearer means that the first logical identifier is associated with the first bearer.

[0175] As an embodiment, the first logical identifier being associated with the first bearer means that: the first bearer is associated with at least one logical identifier, and the first logical identifier is one of the at least one logical identifier.

[0176] As an embodiment, the first logical identifier being associated with the first bearer means that: the first logical identifier is associated with at least one bearer, and the first bearer is one of the at least one bearer.

[0177] As an embodiment, the first logical identifier being associated with the first bearer means that the RLC entity corresponding to the first logical identifier is linked to the PDCP entity corresponding to the first bearer.

[0178] As an embodiment, the first logical identifier being associated with the first bearer means that the RLC entity corresponding to the first logical identifier can deliver the SDU to the PDCP entity corresponding to the first bearer.

[0179] As an embodiment, the first logical identifier being associated with the first bearer means that the PDCP entity corresponding to the first bearer can deliver the PDU to the RLC entity corresponding to the first logical identifier.

[0180] As an embodiment, the discarding is discard.

[0181] As an embodiment, the discard is clear.

[0182] As an embodiment, the discarding is clean.

[0183] As an embodiment, the discarding is delete.

[0184] As an embodiment, the first MAC subPDU is discarded at the MAC sublayer.

[0185] As an embodiment, the first MAC subPDU is discarded by the first MAC entity.

[0186] As an embodiment, discarding the first MAC subPDU includes: not reading the MAC SDU in the first MAC subPDU.

[0187] As an embodiment, discarding the first MAC subPDU includes: not delivering the MAC SDU in the first MAC subPDU to an upper layer.

[0188] As an embodiment, the discarding of the first MAC subPDU includes: not executing the MAC SDU in the first MAC subPDU.

[0189] As an embodiment, the discarding of the first MAC subPDU includes: considering the first MAC subPDU to be an erroneous MAC subPDU.

[0190] As an embodiment, discarding the first MAC subPDU includes: considering the first MAC subPDU as at least one of unknown, unforeseeable and erroneous protocol data.

[0191] As an embodiment, in response to the first MAC PDU being received, the first MAC subPDU is discarded when performing the disassembly and demultiplexing process.

[0192] As an embodiment, in response to the first MAC PDU being received, the first MAC subPDU is discarded when processing unknown, unforeseen and erroneous protocol data.

[0193] As an embodiment, as a response to the first MAC PDU being received, when to discard the first MAC subPDU depends on the UE implementation.

[0194] As an embodiment, in response to the first MAC PDU being received, when the last MAC subPDU in the first MAC PDU is received, the first MAC subPDU is discarded.

[0195] As an embodiment, in response to the first MAC PDU being received, when the first MAC subPDU is received, the first MAC subPDU is discarded.

[0196] As an embodiment, in response to the first MAC PDU being received, the first MAC subPDU is discarded when the MAC subheader in the first MAC subPDU is received.

[0197] As an embodiment, in response to the first MAC PDU being received, when the first logical identifier is determined, the first MAC subPDU is discarded.

[0198] As an embodiment, in response to the first MAC PDU being received, when it is determined that the first logical identifier is associated with the first bearer and the first bearer is suspended, the first MAC subPDU is discarded.

[0199] As an embodiment, in response to the first MAC PDU being received, when it is determined that the first logical identifier is associated with the first bearer and the first bearer is only associated with G-RNTIs other than the first G-RNTI, the first MAC subPDU is discarded.

[0200] As an embodiment, in response to the first MAC PDU being received, the first MAC PDU is discarded; the discarding of the first MAC PDU includes discarding the first MAC subPDU.

[0201] As an embodiment, in response to the first MAC PDU being received, the first MAC subPDU in the first MAC PDU and all remaining MAC subPDUs in the first MAC PDU are discarded.

[0202] As an embodiment, in response to the first MAC PDU being received, only the first MAC subPDU in the first MAC PDU is discarded.

[0203] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast.

[0204] As an embodiment, the "discarding the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast" means: if the first bearer is suspended and the first MAC PDU is received via non-unicast, the first MAC subPDU is discarded.

[0205] As an embodiment, the "discarding the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast" means: if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, the first MAC subPDU is discarded.

[0206] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via a side link.

[0207] As an embodiment, "the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received through the side link" means: if the first bearer is suspended and the first MAC PDU is received through the side link, the first MAC subPDU is discarded.

[0208] As an embodiment, the "discarding the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received through the side link" means: if at least the first bearer is suspended and the first MAC PDU is received through the side link, the first MAC subPDU is discarded.

[0209] As an embodiment, the discarding of the first MAC subPDU depending on the first bearer being suspended means: when the first bearer is suspended, the first MAC subPDU is discarded.

[0210] As an embodiment, the discarding of the first MAC subPDU depending on whether the first bearer is suspended means: if the first bearer is suspended, discarding the first MAC subPDU.

[0211] As an embodiment, the discarding of the first MAC subPDU depending on the suspension of the first bearer means that the suspension of the first bearer triggers the discarding of the first MAC subPDU.

[0212] As an embodiment, the first bearer being suspended means that the first bearer is paused.

[0213] As an embodiment, the first bearer being suspended means that the first bearer is stopped.

[0214] As an embodiment, the first bearer being suspended means that the first bearer is not allowed to send or receive at least one of the two.

[0215] As an embodiment, the non-unicast means that the receivers of the first MAC PDU include multiple nodes.

[0216] As an embodiment, the non-unicast means that the first MAC PDU is directed to multiple nodes.

[0217] As an embodiment, the non-unicast means that the first MAC PDU is common to multiple nodes.

[0218] As an embodiment, the first node is one of the multiple nodes.

[0219] As an embodiment, the non-unicast is group cast.

[0220] As an embodiment, the non-unicast is for V2X.

[0221] As an embodiment, the non-unicast is multicast.

[0222] As an embodiment, the non-unicast is for MBS.

[0223] As an embodiment, the non-unicast is for multicast MBS.

[0224] As an embodiment, the first MAC PDU is received through non-unicast, which means that the first MAC PDU is received through non-unicast.

[0225] As an embodiment, the first MAC PDU is received through non-unicast, which means that the first MAC PDU is received through non-unicast, and the first MAC PDU is received through a side link.

[0226] As an embodiment, the first MAC PDU is received through non-unicast, which means that the first MAC PDU is received through non-unicast, and the first MAC PDU is for MBS.

[0227] As an embodiment, the first MAC PDU is received through non-unicast, which means that the first MAC PDU is received through a side link, and the first MAC PDU is received through unicast.

[0228] As an embodiment, the discarding of the first MAC subPDU relies on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received through the first RNTI.

[0229] As an embodiment, the "discarding the first MAC subPDU depends on the first bearer being associated with an RNTI other than the first RNTI, wherein the first MAC PDU is received through the first RNTI" means: if the first bearer is associated with an RNTI other than the first RNTI and the first MAC PDU is received through the first RNTI, the first MAC subPDU is discarded.

[0230] As an embodiment, the "discarding the first MAC subPDU depends on the first bearer being associated with an RNTI other than the first RNTI, wherein the first MAC PDU is received through the first RNTI" means: if at least the first bearer is associated with an RNTI other than the first RNTI and the first MAC PDU is received through the first RNTI, the first MAC subPDU is discarded.

[0231] As an embodiment, the discarding of the first MAC subPDU depending on the first bearer being associated only with an RNTI other than the first RNTI means: when the first bearer is associated only with a G-RNTI other than the first RNTI, discarding the first MAC subPDU.

[0232] As an embodiment, the discarding of the first MAC subPDU depending on the first bearer being associated only with an RNTI other than the first RNTI means: if the first bearer is associated only with a G-RNTI other than the first RNTI, discarding the first MAC subPDU.

[0233] As an embodiment, the discarding of the first MAC subPDU depending on the first bearer being associated only with an RNTI other than the first RNTI means that the first bearer being associated only with a G-RNTI other than the first RNTI triggers the discarding of the first MAC subPDU.

[0234] As an embodiment, the first bearer being associated with an RNTI other than the first RNTI means that the first bearer is not associated with the first RNTI.

[0235] As an embodiment, the first bearer being associated with an RNTI other than the first RNTI means that any LCID associated with the first bearer is associated with an RNTI other than the first RNTI.

[0236] As an embodiment, the first bearer being associated with an RNTI other than the first RNTI means that any LCID associated with the first bearer is not associated with the first RNTI.

[0237] As an embodiment, the first bearer is associated with an RNTI other than the first RNTI, which means that the first RNTI and the first bearer are not indicated by the same RRC domain.

[0238] As an embodiment, the first bearer is associated with an RNTI other than the first RNTI, which means that at least one bearer is configured for the first RNTI, and the first bearer is not any one of the at least one bearer.

[0239] As an embodiment, an RNTI other than the first RNTI to which the first bearer is associated is configured.

[0240] As an embodiment, the first bearer is associated with an RNTI other than the first RNTI.

[0241] As an embodiment, the first bearer is associated with multiple RNTIs other than the first RNTI.

[0242] As an embodiment, the discarding of the first MAC subPDU depends on the first bearer being suspended and the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than the first RNTI.

[0243] As an embodiment, “the discarding of the first MAC subPDU depends on the first bearer being suspended and the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than the first RNTI” means: if the first bearer is suspended and the first bearer is associated with an RNTI other than the first RNTI, discard the first MAC subPDU.

[0244] As an embodiment, the "discarding the first MAC subPDU depends on the first bearer being suspended and the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than the first RNTI" means: if at least the first bearer is suspended and the first bearer is associated with an RNTI other than the first RNTI, the first MAC subPDU is discarded.

[0245] As an embodiment, a first MAC PDU is received; wherein, the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, the first MAC subPDU is discarded.

[0246] As an embodiment, a first MAC PDU is received; wherein, the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is suspended and the first MAC PDU is received via a secondary link, the first MAC subPDU is discarded.

[0247] As an embodiment, a first MAC PDU is received; wherein, the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is associated with an RNTI other than a first RNTI and the first MAC PDU is received via the first RNTI, the first MAC subPDU is discarded.

[0248] As an embodiment, a first MAC PDU is received; wherein, the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, or, if at least the first bearer is suspended and the first MAC PDU is received via a side link, the first MAC subPDU is discarded.

[0249] As an embodiment, a first MAC PDU is received; wherein, the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, or, if at least the first bearer is associated to an RNTI other than a first RNTI and the first MAC PDU is received via the first RNTI, the first MAC subPDU is discarded.

[0250] As an embodiment, a first MAC PDU is received; wherein, the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is suspended and the first MAC PDU is received via a side link, or, if at least the first bearer is associated to an RNTI other than a first RNTI and the first MAC PDU is received via the first RNTI, the first MAC subPDU is discarded.

[0251] As an embodiment, a first MAC PDU is received; wherein, the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, or, if at least the first bearer is suspended and the first MAC PDU is received via a side link, or, if at least the first bearer is associated with an RNTI other than a first RNTI and the first MAC PDU is received via the first RNTI, the first MAC subPDU is discarded.

[0252] As an embodiment, optionally, as a response to the first MAC PDU being received, if the LCID or eLCID included in a MAC subPDU in the first MAC PDU is not configured, the MAC subPDU is discarded.

[0253] As an embodiment, optionally, as a response to the first MAC PDU being received, if the LCID or eLCID included in a MAC subPDU in the first MAC PDU is reserved, the MAC subPDU is discarded.

[0254] As an embodiment, optionally, as a response to the first MAC PDU being received, if the LCID or eLCID included in a MAC subPDU in the first MAC PDU is reserved, the one MAC subPDU and any remaining MAC subPDU in the first MAC PDU are discarded.

[0255] As an embodiment, optionally, as a response to the first MAC PDU being received, if the first node does not support the LCID or eLCID included in a MAC subPDU in the first MAC PDU, the MAC subPDU is discarded.

[0256] As an embodiment, optionally, as a response to the first MAC PDU being received, if the first node does not support the LCID or eLCID included in a MAC subPDU in the first MAC PDU, the one MAC subPDU and any remaining MAC subPDU in the first MAC PDU are discarded.

[0257] As an embodiment, optionally, as a response to the first MAC PDU being received, if a MAC subPDU including a MAC CE in the first MAC PDU is located after a MAC subPDU including a MAC SDU in the first MAC PDU, at least one of the MAC subPDU including a MAC CE or the MAC subPDU including a MAC SDU is discarded; the first MAC PDU is identified by a first G-RNTI.

[0258] Example 2

[0259] Embodiment 2 illustrates a schematic diagram of a network architecture according to an embodiment of the present application, as shown in FIG2 . FIG2 illustrates a network architecture 200 . The network architecture 200 is a 5G NR (New Radio) / LTE (Long-Term Evolution) / LTE-A (Long-Term Evolution Advanced) system, or the network architecture 200 is a 5G+ network architecture, or the network architecture 200 is a 6G network architecture, or the network architecture 200 is a network architecture that will continue to evolve in the future by 3GPP; the network architecture 200 may be called a 5GS (5G System) / EPS (Evolved Packet System), or the network architecture 200 may be called a 6GS (6G System); the network architecture 200 includes at least one of a UE (User Equipment) 201, a RAN (Radio Access Network) 202, a core network 210, an HSS (Home Subscriber Server) / UDM (Unified Data Management) 220, and an Internet service 230. The network architecture 200 can interconnect with other access networks, but for simplicity, these entities / interfaces are not shown. As shown, the network architecture 200 provides packet-switched services, but 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. The RAN includes node 203 and other nodes 204. Node 203 provides user and control plane protocol termination towards UE 201. Node 203 can be connected to other nodes 204 via an Xn interface (e.g., backhaul) / X2 interface. Node 203 may also be referred to as a base station, base transceiver station, radio base station, radio transceiver, transceiver function, basic service set (BSS), extended service set (ESS), TRP (transmitter / receiver node), or some other appropriate terminology. The core network 210 is a 5G Core Network (5G Core Network) / EPC (Evolved Packet Core), or alternatively, a 6G Core Network; node 203 provides an access point to the core network 210 for UE 201.Examples of UE 201 include cellular phones, smart phones, Session Initiation Protocol (SIP) phones, laptop computers, personal digital assistants (PDAs), satellite radios, non-terrestrial base station communications, satellite mobile communications, global positioning systems, multimedia devices, video devices, digital audio players (e.g., MP3 players), cameras, game consoles, drones, aircraft, narrowband Internet of Things devices, machine type communication devices, land vehicles, cars, wearable devices, or any other similar functional devices. Those skilled in the art may also refer to UE 201 as a mobile station, subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term. Node 203 is connected to the core network 210 via an S1 / NG interface. The core network 210 includes the MME (Mobility Management Entity) / AMF (Authentication Management Field) / SMF (Session Management Function) 211, other MMEs / AMFs / SMFs 214, the S-GW (Service Gateway) / UPF (User Plane Function) 212, and the P-GW (Packet Data Network Gateway) / UPF 213. The MME / AMF / SMF 211 is the control node that handles signaling between the UE 201 and the core network 210. Generally, the MME / AMF / SMF 211 provides bearer and connection management. All user Internet Protocol (IP) packets are transmitted through the S-GW / UPF 212, which is itself connected to the P-GW / UPF 213. The P-GW provides UE IP address allocation and other functions. The P-GW / UPF 213 is connected to the Internet service 230. Internet services 230 include operator-specific Internet protocol services, which may include the Internet, intranet, IMS (IP Multimedia Subsystem), and packet-switched streaming services.

[0260] As an embodiment, the UE 201 is a user equipment (UE).

[0261] As an embodiment, the UE 201 is a base station (BS).

[0262] As an embodiment, the UE 201 is a relay device.

[0263] As an embodiment, the UE 201 is a gateway device.

[0264] As an embodiment, the node 203 corresponds to the second node in this application.

[0265] As an embodiment, the node 203 is a base station device.

[0266] As an embodiment, the node 203 is a user equipment.

[0267] As an embodiment, the node 203 is a relay device.

[0268] As an embodiment, the node 203 is a gateway device.

[0269] Typically, the UE 201 is a user equipment, and the node 203 is a base station device.

[0270] Typically, the UE 201 is a user equipment, and the node 203 is a user equipment.

[0271] Typically, the UE 201 is a base station device, and the node 203 is a base station device.

[0272] As an embodiment, the user equipment supports transmission of a non-terrestrial network (NTN).

[0273] As an embodiment, the user equipment supports transmission via a terrestrial network (Terrestrial Network).

[0274] As an embodiment, the user equipment supports dual connection (DC) transmission.

[0275] As an embodiment, the user equipment supports V2X.

[0276] As an embodiment, the user equipment supports multicast MBS.

[0277] As an embodiment, the user equipment supports multicast MBS and V2X.

[0278] As an embodiment, the user equipment supports RRC_INACTIVE multicast MBS.

[0279] As an embodiment, the user equipment supports RRC_INACTIVE multicast MBS and V2X.

[0280] As an embodiment, the user equipment includes an aircraft.

[0281] As an embodiment, the user equipment includes a vehicle-mounted terminal.

[0282] As an embodiment, the user equipment includes a vessel.

[0283] As an embodiment, the user equipment includes an Internet of Things terminal.

[0284] As an embodiment, the user equipment includes a terminal of the Industrial Internet of Things.

[0285] As an embodiment, the user equipment includes a device that supports low-latency and high-reliability transmission.

[0286] As an embodiment, the user equipment includes a test device.

[0287] As an embodiment, the user equipment includes a signaling tester.

[0288] As an embodiment, the user equipment includes an IAB (Integrated Access and Backhaul)-MT.

[0289] As an embodiment, the base station device supports transmission in a non-terrestrial network.

[0290] As an embodiment, the base station device supports transmission of a terrestrial network.

[0291] As an embodiment, the base station equipment includes a base transceiver station (Base Transceiver Station, BTS).

[0292] As an embodiment, the base station device includes a Node B (NB).

[0293] As an embodiment, the base station device includes a gNB.

[0294] As an embodiment, the base station device includes an eNB.

[0295] As an embodiment, the base station device includes ng-eNB.

[0296] As an embodiment, the base station device includes an en-gNB.

[0297] As an embodiment, the base station device includes a CU (Centralized Unit).

[0298] As an embodiment, the base station device includes a DU (Distributed Unit).

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

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

[0301] As an embodiment, the base station device includes a micro cell base station.

[0302] As an embodiment, the base station device includes a pico cell (Pico Cell) base station.

[0303] As an embodiment, the base station device includes a home base station (Femtocell).

[0304] As an embodiment, the base station device includes a flying platform device.

[0305] As an embodiment, the base station device includes a satellite device.

[0306] As an embodiment, the base station device includes a testing device.

[0307] As an embodiment, the base station equipment includes a signaling tester.

[0308] As an embodiment, the base station device includes a gateway device.

[0309] As an embodiment, the base station device includes an IAB-node.

[0310] As an embodiment, the base station device includes an IAB-donor.

[0311] As an embodiment, the base station device includes an IAB-donor-CU.

[0312] As an embodiment, the base station device includes an IAB-donor-DU.

[0313] As an embodiment, the base station device includes an IAB-DU.

[0314] As an embodiment, the base station device includes an IAB-MT.

[0315] As an embodiment, the relay device includes a relay.

[0316] As an embodiment, the relay device includes an L3 relay.

[0317] As an embodiment, the relay device includes an L2 relay.

[0318] As an embodiment, the relay device includes a router.

[0319] As an embodiment, the relay device includes a switch.

[0320] As an embodiment, the relay device includes a gateway device.

[0321] As an embodiment, the relay device includes user equipment.

[0322] As an embodiment, the relay device includes a base station device.

[0323] Example 3

[0324] Embodiment 3 illustrates a schematic diagram of an embodiment of a radio protocol architecture for a user plane and a control plane according to the present application, as shown in FIG3 . FIG3 is a schematic diagram illustrating an embodiment of a radio protocol architecture for a user plane 350 and a control plane 300. FIG3 illustrates the radio protocol architecture for the control plane 300 using three layers: Layer 1, Layer 2, and Layer 3. Layer 1 (L1 layer) is the lowest layer and implements various PHY (physical layer) signal processing functions. The L1 layer will be referred to herein as PHY 301. 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 supports inter-zone mobility. 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 (Hybrid Automatic Repeat Request). 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) within a cell. The MAC sublayer 302 is also responsible for HARQ operations. The RRC (Radio Resource Control) sublayer 306 in Layer 3 (L3) of the control plane 300 is responsible for obtaining radio resources (i.e., radio bearers) and configuring lower layers using RRC signaling. The radio protocol architecture of the user plane 350 includes Layer 1 (L1) and Layer 2 (L2). The radio protocol architecture in the user plane 350 is generally identical to the corresponding layers and sublayers in the control plane 300, including 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. However, the PDCP sublayer 354 also provides header compression for upper layer packets to reduce radio transmission overhead. The L2 layer 355 in the user plane 350 also includes the SDAP (Service Data Adaptation Protocol) sublayer 356, which is responsible for mapping QoS flows to data radio bearers (DRBs) to support service diversity.

[0325] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the first node in this application.

[0326] As an embodiment, the wireless protocol architecture in FIG3 is applicable to the second node in this application.

[0327] As an embodiment, the first MAC PDU in the present application is generated at a higher layer of the PDCP304.

[0328] As an embodiment, the first MAC PDU in the present application is generated by the PDCP304.

[0329] As an embodiment, the first MAC PDU in the present application is generated at a higher layer of the RRC306.

[0330] As an embodiment, the first MAC PDU in the present application is generated in the RRC306.

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

[0332] As an embodiment, the first RRC message in this application is generated in the RRC306.

[0333] Example 4

[0334] Embodiment 4 shows a schematic diagram of a first communication device and a second communication device according to the present application, as shown in Figure 4. 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.

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

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

[0337] During transmission from the second communication device 410 to the first communication device 450, upper layer data packets from the core network are provided to the controller / processor 475 at the second communication device 410. The controller / processor 475 implements L2 layer functionality. During 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), and M-quadrature amplitude modulation (M-QAM)). The multi-antenna transmit processor 471 performs digital spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming 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 and / or frequency domain, and then uses an inverse fast Fourier transform (IFFT) to generate a physical channel carrying the time-domain multicarrier symbol stream. The multi-antenna transmit processor 471 then performs transmit analog precoding / beamforming operations on the time-domain multicarrier 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.

[0338] During 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 via 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, which is provided to the receive processor 456. The receive processor 456 and the multi-antenna receive processor 458 implement various L1 signal processing functions. The multi-antenna receive processor 458 performs receive analog precoding / beamforming operations on the baseband multi-carrier symbol stream from the receiver 454. The receive processor 456 converts the baseband multi-carrier symbol stream, after the receive analog precoding / beamforming operations, from the time domain to the frequency domain using a fast Fourier transform (FFT). In the frequency domain, the receive processor 456 demultiplexes the physical layer data signal and reference signal, where the reference signal is used for channel estimation. The data signal undergoes multi-antenna detection in the multi-antenna receive processor 458 to recover any spatial streams destined for the first communication device 450. The symbols on each spatial stream are demodulated and recovered in the receive processor 456, and soft decisions are generated. The receive processor 456 then decodes and deinterleaves the soft decisions to recover the upper layer data and control signals transmitted by the second 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 code and data. The memory 460 may be referred to as a computer-readable medium. During transmission from the second communication device 410 to the first communication device 450, the controller / processor 459 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover 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 the L3 layer for L3 processing.

[0339] During transmission from the first communication device 450 to the second communication device 410, a data source 467 is used at the first communication device 450 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 functionality 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, implementing L2 layer functions for the user plane and control plane. The controller / processor 459 is also responsible for retransmission of lost packets and signaling to the second communication device 410. The transmit processor 468 performs modulation mapping and channel coding, while the multi-antenna transmit processor 457 performs digital multi-antenna spatial precoding, including codebook-based and non-codebook-based precoding, and beamforming. The transmit processor 468 then modulates the resulting spatial stream into a multi-carrier / single-carrier symbol stream. After analog precoding and beamforming operations in the multi-antenna transmit processor 457, the stream is provided to different antennas 452 via the transmitter 454. Each transmitter 454 first converts the baseband symbol stream provided by the multi-antenna transmit processor 457 into a RF symbol stream before providing it to the antenna 452.

[0340] During transmission from the first communications device 450 to the second communications device 410, the functionality at the second communications device 410 is similar to the reception functionality at the first communications device 450 described for transmission from the second communications device 410 to the first communications device 450. Each receiver 418 receives RF signals via its corresponding antenna 420, converts the received RF signals into baseband signals, and provides the baseband signals to a multi-antenna receive processor 472 and a receive processor 470. The receive processor 470 and the multi-antenna receive processor 472 collectively implement L1 layer functionality. A controller / processor 475 implements L2 layer functionality. The controller / processor 475 may be associated with a memory 476 storing program codes and data. The memory 476 may be referred to as a computer-readable medium. During transmission from the first communications device 450 to the second communications device 410, the controller / processor 475 provides demultiplexing between transport and logical channels, packet reassembly, decryption, header decompression, and control signal processing to recover upper layer data packets from the UE 450. Upper layer packets from controller / processor 475 may be provided to the core network.

[0341] 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: receives a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, discards the first MAC subPDU; wherein the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a side link; or, the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0342] As an embodiment, the first communication device 450 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: receiving a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicating a first logical identifier, the first logical identifier being configured, and the first logical identifier being associated with a first bearer; as a response to the first MAC PDU being received, discarding the first MAC subPDU; wherein the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a side link; or, the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0343] 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: sends a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; as a response to the first MAC PDU being received, the receiver of the first MAC PDU discards the first MAC subPDU; wherein the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link; or, the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0344] As an embodiment, the second communication device 410 includes: a memory storing a computer-readable instruction program, the computer-readable instruction program generating actions when executed by at least one processor, the actions including: sending a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicating a first logical identifier, the first logical identifier being configured, and the first logical identifier being associated with a first bearer; as a response to the first MAC PDU being received, the receiver of the first MAC PDU discards the first MAC subPDU; wherein the discarding of the first MAC subPDU depends on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or, the first MAC PDU is received via a side link; or, the discarding of the first MAC subPDU depends on the first bearer being associated with an RNTI other than the first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0345] As an embodiment, at least one of the antenna 452, the receiver 454, the receive processor 456, and the controller / processor 459 is used to receive a first MAC PDU.

[0346] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller / processor 475 is used to transmit a first MAC PDU.

[0347] As an embodiment, at least one of the antenna 452, the receiver 454, the receiving processor 456, and the controller / processor 459 is used to receive a first RRC message.

[0348] As an embodiment, at least one of the antenna 420, the transmitter 418, the transmit processor 416, and the controller / processor 475 is used to send a first RRC message.

[0349] As an embodiment, the first communication device 450 corresponds to the first node in this application.

[0350] As an embodiment, the second communication device 410 corresponds to the second node in this application.

[0351] As an embodiment, the first communication device 450 is a user equipment.

[0352] As an embodiment, the first communication device 450 is a base station device.

[0353] As an embodiment, the first communication device 450 is a relay device.

[0354] As an embodiment, the second communication device 410 is a user equipment.

[0355] As an embodiment, the second communication device 410 is a base station device.

[0356] As an embodiment, the second communication device 410 is a relay device.

[0357] Example 5

[0358] Example 5 illustrates a wireless signal transmission flow chart according to an embodiment of the present application, as shown in FIG5. It should be noted that the order in this example does not limit the signal transmission order and implementation order in the present application.

[0359] For the first node U01, in step S5101, a first MAC PDU is received; wherein, the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in step S5102, as a response to the reception of the first MAC PDU, the first MAC subPDU is discarded.

[0360] For the second node N02, in step S5201, the first MAC PDU is sent.

[0361] For the third node N03, in step S5301, the first MAC PDU is received.

[0362] In embodiment 5, the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast.

[0363] As an embodiment, the first node U01 and the second node N02 are connected via a Uu port.

[0364] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a user equipment.

[0365] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a relay device.

[0366] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a base station device.

[0367] As an embodiment, the user equipment is a UE and the base station device is a gNB.

[0368] As an embodiment, step S5301 is optional.

[0369] As an embodiment, step S5301 does not exist.

[0370] As an embodiment, step S5301 exists.

[0371] As an embodiment, the third node N03 is optional.

[0372] As an embodiment, the third node N03 does not exist.

[0373] As an embodiment, the third node N03 exists.

[0374] As an embodiment, the third node N03 is a node other than the first node U01.

[0375] As an embodiment, the third node N03 is a user equipment.

[0376] As an embodiment, the third node N03 is a relay.

[0377] As an embodiment, the third node N03 is a base station device.

[0378] As an embodiment, the first node U01 receives the first MAC PDU in the RRC_CONNECTED state; the third node N03 receives the first MAC PDU in the RRC_CONNECTED state.

[0379] As an embodiment, the first node U01 receives the first MAC PDU in the RRC_CONNECTED state; the third node N03 receives the first MAC PDU in the RRC_INACTIVE state.

[0380] As an embodiment, the first node U01 receives the first MAC PDU in the RRC_INACTIVE state; the third node N03 receives the first MAC PDU in the RRC_CONNECTED state.

[0381] As an embodiment, the first node U01 receives the first MAC PDU in the RRC_INACTIVE state; the third node N03 receives the first MAC PDU in the RRC_INACTIVE state.

[0382] As an embodiment, optionally, the second node N02 configures the first logical identifier to the first node U01 and the third node N03.

[0383] As an embodiment, optionally, the second node N02 configures the first bearer to the first node U01 and the third node N03.

[0384] As an embodiment, optionally, as a response to the first MAC PDU being received, the first MAC subPDU is not discarded by the third node N03; and the first bearer is not suspended by the third node N03.

[0385] As an embodiment, optionally, as a response to the first MAC PDU being received, the first MAC subPDU is discarded by the third node N03; and the first bearer is suspended by the third node N03.

[0386] As an embodiment, the non-unicast is multicast.

[0387] As an embodiment, the non-unicast is multicast.

[0388] As an embodiment, the first bearer is an MRB (MBS Radio Bearer).

[0389] As an embodiment, the first bearer is a multicast MRB.

[0390] As an embodiment, the first bearer is added by an MRB-ToAddModList field.

[0391] As an embodiment, the first bearer is indicated by an MRB-Identity.

[0392] As an embodiment, the first bearer is indicated by an MRB-Identity.

[0393] As an embodiment, the first logical identifier is configured by an MRB-RLC-ConfigMulticast domain.

[0394] As an embodiment, the first logical identifier is configured by an MBS-SessionInfoListMulticast IE.

[0395] As an embodiment, the first logical identifier is associated with the first bearer by an MRB-InfoMulticast configuration.

[0396] As an embodiment, the first logical identifier is associated with the first bearer by an MRB-InfoMulticast configuration.

[0397] As an embodiment, the first logical identifier is associated with the first bearer by an RLC-BearerConfig configuration.

[0398] As an embodiment, the first MAC PDU is received via a configured downlink allocation; the first bearer is associated to the configured downlink allocation.

[0399] As an embodiment, the first MAC PDU is received via a configured downlink allocation; the first bearer is not associated with the configured downlink allocation.

[0400] As an embodiment, the first MAC PDU is received via a first RNTI; and the first bearer is associated with an RNTI other than the first RNTI.

[0401] As an embodiment, the first MAC PDU is received via a first RNTI; the first bearer is associated with the first RNTI.

[0402] As an embodiment, the first MAC PDU is received through the first RNTI, which means that the first MAC PDU is for the first RNTI.

[0403] As an embodiment, the first MAC PDU is received through the first RNTI, which means that the first MAC PDU is identified by the first RNTI.

[0404] As an embodiment, the first MAC PDU is received through the first RNTI, which means that the first MAC PDU is scheduled by the first RNTI.

[0405] As an embodiment, the first MAC PDU is received through the first RNTI, which means that the CRC of the DCI that schedules the first MAC PDU is scrambled by the first RNTI.

[0406] As an embodiment, the first bearer being associated with the first RNTI means that: the first RNTI and the first bearer are indicated by the same RRC domain.

[0407] As an embodiment, the first bearer being associated with the first RNTI means that the first RNTI and the first bearer are indicated by the same MBS-SessionInfo field.

[0408] As an embodiment, the first bearer being associated with the first RNTI means that the first RNTI and the first bearer are indicated by the same MBS-SessionInfoMulticast field.

[0409] As an embodiment, the first bearer being associated with the first RNTI means that the multicast MBS session corresponding to the first RNTI can be transmitted through the first bearer.

[0410] As an embodiment, the first bearer being associated with the first RNTI means that at least one bearer is configured for the first RNTI, and the first bearer is one of the at least one bearer.

[0411] As an embodiment, the first RNTI is a G-RNTI.

[0412] As an embodiment, the first RNTI is used to receive a multicast MBS.

[0413] As an embodiment, the first RNTI is used to receive the multicast MBS in the RRC_CONNECTED state.

[0414] As an embodiment, the first RNTI is used to receive the multicast MBS in the RRC_INACTIVE state.

[0415] As an embodiment, the first RNTI is used to receive the multicast MBS in the RRC_IDLE state.

[0416] As an embodiment, the “if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, discard the first MAC subPDU” means: if the first bearer is suspended and the first MAC PDU is received via non-unicast and the non-unicast is multicast, discard the first MAC subPDU.

[0417] As an embodiment, the “if at least the first bearer is suspended and the first MAC PDU is received via non-unicast, discard the first MAC subPDU” means: if at least the first bearer is suspended and the first MAC PDU is received via non-unicast and the non-unicast is multicast, discard the first MAC subPDU.

[0418] Example 6

[0419] Example 6 illustrates a wireless signal transmission flow chart according to another embodiment of the present application, as shown in Figure 6. It should be noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0420] For the first node U01, in step S6101, a first MAC PDU is received; wherein, the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in step S6102, as a response to the reception of the first MAC PDU, the first MAC subPDU is discarded.

[0421] For the second node N02, in step S6201, the first MAC PDU is sent.

[0422] In embodiment 6, the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via a secondary link.

[0423] As an embodiment, the first node U01 and the second node N02 are connected via the PC5 port.

[0424] As an embodiment, the first node U01 and the second node N02 are connected via a V2X interface.

[0425] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a user equipment.

[0426] As an embodiment, the first MAC PDU is received through dynamic scheduling.

[0427] As an embodiment, the first MAC PDU is received via a configured downlink assignment.

[0428] As an embodiment, the first MAC PDU is received through the secondary link, which means that the first MAC PDU is received on the secondary link.

[0429] As an embodiment, the first MAC PDU is received through the secondary link, which means that the first MAC PDU is received on the SL-SCH.

[0430] As an embodiment, the first bearer is a wireless bearer of SL.

[0431] As an embodiment, the first bearer is an SL-SRB3.

[0432] As an embodiment, the first bearer is SRB1.

[0433] As an embodiment, the first bearer is split SRB1.

[0434] As an embodiment, the first bearer is configured by an SL-RemoteUE-RB-Identity.

[0435] As an embodiment, the first bearer is configured by an SRB-Identity.

[0436] As an embodiment, the first bearer is configured by an sl-SRB-Identity.

[0437] As an embodiment, the first bearer is configured by an SRB-Identity.

[0438] As an embodiment, the first bearer is configured by an SL-RLC-BearerConfig.

[0439] As an embodiment, the first logical identifier is unicast.

[0440] As an embodiment, the first logical identifier is multicast.

[0441] As an embodiment, the first logical identifier is configured for the secondary link.

[0442] As an embodiment, the first logical identifier is unicast of the secondary link.

[0443] As an embodiment, the first logical identifier is for multicast of the secondary link.

[0444] As an embodiment, the first logical identifier is associated with the first bearer by a SL-RLC-BearerConfig configuration.

[0445] As an embodiment, the first logical identifier is associated with the first bearer by an SLRB-Config configuration.

[0446] As an embodiment, the first logical identifier is associated to the first bearer by an SL-MappingToAddMod configuration.

[0447] As an embodiment, the first node is configured with multi-path, and the first MAC PDU is received through an indirect path.

[0448] As an embodiment, the "if at least the first bearer is suspended and the first MAC PDU is received through the side link, discard the first MAC subPDU" means: if the first bearer is suspended and the first MAC PDU is received through the side link and the first logical identifier is unicast, discard the first MAC subPDU.

[0449] As an embodiment, the "if at least the first bearer is suspended and the first MAC PDU is received through the side link, discard the first MAC subPDU" means: if at least the first bearer is suspended and the first MAC PDU is received through the side link and the first logical identifier is unicast, discard the first MAC subPDU.

[0450] Example 7

[0451] Embodiment 7 illustrates a wireless signal transmission flow chart according to another embodiment of the present application, as shown in FIG7. It should be noted that the order in this example does not limit the signal transmission order and implementation order in this application.

[0452] For the first node U01, in step S7101, a first MAC PDU is received; wherein, the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in step S7102, as a response to the reception of the first MAC PDU, the first MAC subPDU is discarded.

[0453] For the second node N02, in step S7201, the first MAC PDU is sent.

[0454] For the third node N03, in step S7301, the first MAC PDU is received.

[0455] In embodiment 7, the discarding of the first MAC subPDU is dependent on the first bearer being associated with an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0456] As an embodiment, the first node U01 and the second node N02 are connected via a Uu port.

[0457] As an embodiment, the first node U01 and the second node N02 are connected via an NR Uu port.

[0458] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a user equipment.

[0459] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a relay device.

[0460] As an embodiment, the first node U01 is a user equipment, and the second node N02 is a base station device.

[0461] As an embodiment, the user equipment is a UE and the base station device is a gNB.

[0462] As an embodiment, step S5301 is optional.

[0463] As an embodiment, step S5301 does not exist.

[0464] As an embodiment, step S5301 exists.

[0465] As an embodiment, the third node N03 does not exist.

[0466] As an embodiment, the third node N03 exists.

[0467] As an embodiment, the third node N03 is a node other than the first node U01.

[0468] As an embodiment, the third node N03 is a user equipment.

[0469] As an embodiment, the third node N03 is a relay.

[0470] As an embodiment, the third node N03 is a base station device.

[0471] As an embodiment, optionally, the second node N02 configures the first RNTI to the first node U01 and the third node N03.

[0472] As an embodiment, optionally, the second node N02 configures the first logical identifier to the first node U01 and the third node N03.

[0473] As an embodiment, optionally, the second node N02 configures the first bearer to the first node U01 and the third node N03.

[0474] As an embodiment, the first bearer is suspended.

[0475] As an embodiment, the first bearer is not suspended.

[0476] As an embodiment, the first bearer is configured with at least one G-RNTI.

[0477] As an embodiment, the first bearer is configured with at least one G-CS-RNTI.

[0478] As an embodiment, the first bearer is not configured with G-CS-RNTI.

[0479] As an embodiment, the first bearer is an MRB (MBS Radio Bearer).

[0480] As an embodiment, the first bearer is a multicast MRB.

[0481] As an embodiment, the first bearer is added by an MRB-ToAddModList field.

[0482] As an embodiment, the first bearer is indicated by an MRB-Identity.

[0483] As an embodiment, the first logical identifier is configured by an MRB-RLC-ConfigMulticast domain.

[0484] As an embodiment, the first logical identifier is configured by an MBS-SessionInfoListMulticast IE.

[0485] As an embodiment, the first logical identifier is associated with the first bearer by an MRB-InfoMulticast configuration.

[0486] As an embodiment, the first logical identifier is associated with the first bearer by an MRB-InfoMulticast configuration.

[0487] As an embodiment, the first logical identifier is associated with the first bearer by an RLC-BearerConfig configuration.

[0488] As an embodiment, the first RNTI is a G-RNTI.

[0489] As an embodiment, the RNTI other than the first RNTI is a G-RNTI.

[0490] As an embodiment, the G-RNTI is for multicast.

[0491] As an embodiment, the first node U01 is not configured with a G-CS-RNTI.

[0492] As an embodiment, the first RNTI is a G-CS-RNTI.

[0493] As an embodiment, the first RNTI is either G-RNTI or G-CS-RNTI.

[0494] As an embodiment, the RNTI other than the first RNTI is a G-CS-RNTI.

[0495] As an embodiment, the first RNTI is G-RNTI; the non-unicast is multicast.

[0496] As an embodiment, the first RNTI is a G-RNTI; the non-unicast is a broadcast.

[0497] Typically, the first RNTI is a G-RNTI; the first logical identifier is an LCID; and the first bearer is a multicast MRB.

[0498] Typically, the first RNTI is a G-RNTI; the first logical identifier is an eLCID; and the first bearer is a multicast MRB.

[0499] Typically, the first RNTI is a G-CS-RNTI; the first logical identifier is an LCID; and the first bearer is a multicast MRB.

[0500] Typically, the first RNTI is a G-CS-RNTI; the first logical identifier is an eLCID; and the first bearer is a multicast MRB.

[0501] Typically, the first RNTI is a G-CS-RNTI; the first logical identifier is an LCID or an eLCID; and the first bearer is a multicast MRB.

[0502] As an embodiment, the first bearer is associated with an RNTI other than the first RNTI, which means that the first RNTI and the first bearer are not indicated by the same MBS-SessionInfo field.

[0503] As an embodiment, the first bearer is associated with an RNTI other than the first RNTI, which means that the first RNTI and the first bearer are not indicated by the same MBS-SessionInfoMulticast field.

[0504] As an embodiment, the first bearer being associated with an RNTI other than the first RNTI means that the multicast MBS session corresponding to the first RNTI is not transmitted through the first bearer.

[0505] As an embodiment, the first bearer being associated with an RNTI other than the first RNTI means that the first bearer is associated with a G-RNTI other than the first RNTI.

[0506] As an embodiment, the first RNTI and the first bearer are associated to an RNTI other than the first RNTI in order to receive multicast MBS.

[0507] As an embodiment, the first RNTI and the first bearer are associated to an RNTI other than the first RNTI in order to receive multicast MBS in RRC_INACTIVE state.

[0508] As an embodiment, the first RNTI and the first bearer are associated to an RNTI other than the first RNTI in order to receive multicast MBS in RRC_CONNECTED state.

[0509] As an embodiment, the first RNTI and the first bearer are associated with RNTIs other than the first RNTI, both of which are G-RNTIs.

[0510] As an embodiment, the "if at least the first bearer is associated to an RNTI other than the first RNTI and the first MAC PDU is received through the first RNTI, discard the first MAC subPDU" means: if the first bearer is associated to an RNTI other than the first RNTI and the first MAC PDU is received through the first RNTI and the first RNTI is a G-RNTI and the non-unicast is multicast, discard the first MAC subPDU.

[0511] As an embodiment, the "if at least the first bearer is associated to an RNTI other than the first RNTI and the first MAC PDU is received through the first RNTI, discard the first MAC subPDU" means: if at least the first bearer is associated to an RNTI other than the first RNTI and the first MAC PDU is received through the first RNTI and the first RNTI is a G-RNTI and the non-unicast is multicast, discard the first MAC subPDU.

[0512] Example 8

[0513] Embodiment 8 illustrates a flow chart of suspending the first bearer according to an embodiment of the present application, as shown in FIG8. It should be noted that the order in this example does not limit the signal transmission order and implementation order in the present application.

[0514] For the first node U01, in step S8101, a first RRC message is received; in response to the receipt of the first RRC message, the RRC_INACTIVE state is maintained and the first bearer is suspended.

[0515] For the second node N02, in step S8201, the first RRC message is sent.

[0516] In embodiment 8, the first RRC message indicates that data is transmitted through at least one bearer in the RRC_INACTIVE state; and the first bearer is a bearer other than the at least one bearer.

[0517] As an embodiment, the first node U01 receives the first RRC message in the RRC_INACTIVE state.

[0518] As an embodiment, the first node U01 receives the first RRC message in the RRC_CONNECTED state.

[0519] As an embodiment, the first RRC message is transmitted via MCCH.

[0520] As an embodiment, the first RRC message is transmitted via DCCH.

[0521] As an embodiment, the first RRC message is an RRCRelease message.

[0522] As an embodiment, the first RRC message is an RRCRelease message, and the message includes a suspendConfig.

[0523] As an embodiment, the first RRC message is a Paging message.

[0524] As an embodiment, the first RRC message is an MBSMulticastConfiguration message.

[0525] As an embodiment, the first RRC message includes an MBSMulticastConfiguration message.

[0526] As an embodiment, the first RRC message includes MBS-SessionInfoListMulticast IE.

[0527] As an embodiment, the first RRC message includes the MBS-SessionInfoMulticast-r18 field.

[0528] As an embodiment, maintaining the RRC_INACTIVE state refers to entering the RRC_INACTIVE state.

[0529] As an embodiment, maintaining the RRC_INACTIVE state means: if the first node U01 is in the RRC_CONNECTED state, entering the RRC_INACTIVE state.

[0530] As an embodiment, maintaining the RRC_INACTIVE state means: if the first node U01 is in the RRC_INACTIVE state, maintaining the RRC_INACTIVE state.

[0531] As an embodiment, the first node U01 first suspends the first bearer and then maintains the RRC_INACTIVE state.

[0532] As an embodiment, the suspending of the first bearer occurs before the maintaining of the RRC_INACTIVE state.

[0533] As an embodiment, when the first RRC message is received, the first bearer is not suspended.

[0534] As an embodiment, in response to the first RRC message being received, the first bearer is suspended only when the first bearer is not suspended.

[0535] As an embodiment, in response to the first RRC message being received, if the first bearer is not suspended, the first bearer is suspended.

[0536] As an embodiment, optionally, as a response to the first RRC message being received, all multicast MRBs that are not indicated to transmit data in the RRC_INACTIVE state are suspended; the first bearer is one of all multicast MRBs that are not indicated to transmit data in the RRC_INACTIVE state.

[0537] As an embodiment, optionally, as a response to the first RRC message being received, all SRBs and DRBs except SRB0 and broadcast MRB are suspended.

[0538] As an embodiment, the first node U01 receives the first MAC PDU in the RRC_INACTIVE state.

[0539] As an embodiment, before the step S5101 in embodiment 5, the step S8101 and the step S8102 are executed.

[0540] As an embodiment, the first bearer is not resumed within the time interval between step S8102 and step S5101.

[0541] As an embodiment, the first bearer is suspended during the time interval between step S8102 and step S5101.

[0542] As an embodiment, when step S5101 is executed, the first bearer is suspended.

[0543] As an embodiment, before the step S6101 in embodiment 6, the step S8101 and the step S8102 are executed.

[0544] As an embodiment, the first bearer is not resumed within the time interval between step S8102 and step S6101.

[0545] As an embodiment, the first bearer is suspended during the time interval between step S8102 and step S6101.

[0546] As an embodiment, when step S6101 is executed, the first bearer is suspended.

[0547] Example 9

[0548] Embodiment 9 illustrates a flow chart of suspending the first bearer according to another embodiment of the present application, as shown in FIG9. It should be noted that the order in this example does not limit the signal transmission order and implementation order in the present application.

[0549] For the first node U01, in step S9101, it is determined that a connection failure occurs; in step S9102, in response to the determination of the connection failure, the first bearer is suspended.

[0550] As an embodiment, determining that a connection failure occurs refers to: considering that the connection failure occurs.

[0551] As an embodiment, determining that a connection failure occurs refers to: considering that the connection failure is detected.

[0552] As an embodiment, determining that a connection failure occurs refers to detecting the connection failure.

[0553] As an embodiment, the connection failure is a radio link failure (Radio Link Failure, RLF).

[0554] As an embodiment, the connection failure is a handover failure.

[0555] As an embodiment, the SCG failure is a synchronous reconfiguration failure (reconfiguration with sync failure).

[0556] As an embodiment, the first node U01 determines that a connection failure occurs in the RRC_CONNECTED state; as a response to the determination of the connection failure, a connection failure information process is initiated, and in the connection failure information process, the first bearer is suspended.

[0557] As an embodiment, the connection failure is an MCG failure (Failure).

[0558] As an embodiment, the MCG failure is an MCG RLF.

[0559] As an embodiment, the MCG failure is an MCG switching failure.

[0560] As an embodiment, the connection failure information process is an MCG failure information process.

[0561] As an embodiment, during the connection failure information process, MCG transmission is suspended; the suspending of MCG transmission includes suspending the first bearer.

[0562] As an embodiment, the suspending MCG transmission includes: suspending MCG transmission for all SRBs and DRBs.

[0563] As an embodiment, the connection failure is an SCG failure.

[0564] As an embodiment, the SCG failure is an SCG RLF.

[0565] As an embodiment, the SCG failure is an SCG synchronous reconfiguration failure.

[0566] As an embodiment, the SCG failure is the SCG configuration failure.

[0567] As an embodiment, the SCG failure is receiving an integrity check failure indication from SCG lower layers concerning SRB3.

[0568] As an embodiment, the connection failure information process is an SCG failure information process.

[0569] As an embodiment, during the connection failure information process, SCG transmission is suspended; the suspending SCG transmission includes suspending the first bearer.

[0570] As an embodiment, the suspending SCG transmission includes: suspending SCG transmission for all SRBs and DRBs.

[0571] As an embodiment, the connection failure is an indirect path failure.

[0572] As an embodiment, the indirect path failure is a secondary link (SL) indirect path failure.

[0573] As an embodiment, the indirect path failure is an N3C indirect path failure (SL indirect path failure).

[0574] As an embodiment, the connection failure information process is an Indirect path failure information process.

[0575] As an embodiment, in the connection failure information process, indirect path transmission is suspended.

[0576] As an embodiment, the suspending of the indirect path transmission includes suspending the first bearer.

[0577] As an embodiment, the suspending the indirect path transmission includes: suspending the indirect path transmission for all SRBs and DRBs.

[0578] As an embodiment, the first node U01 determines that a connection failure occurs in the RRC_INACTIVE state.

[0579] As an embodiment, optionally, as a response to the first MAC PDU being received, the first MAC subPDU is discarded, and the MAC SDU other than the first MAC subPDU in the first MAC PDU is not affected by the discarding of the first MAC subPDU.

[0580] As an embodiment, optionally, as a response to the first MAC PDU being received, the first MAC PDU is discarded, and the discarding of the first MAC PDU includes discarding the first MAC subPDU.

[0581] The above method avoids the impact of inaccurate MAC PDUs received when the link quality is poor.

[0582] As an embodiment, optionally, as a response to the first MAC PDU being received, the first MAC subPDU and all remaining MAC subPDUs in the first MAC PDU are discarded.

[0583] The above method avoids the impact of inaccurate MAC subPDUs received when the link quality is poor.

[0584] As an embodiment, before the step S5101 in embodiment 5, the step S9101 and the step S9102 are executed.

[0585] As an embodiment, the first bearer is not resumed within the time interval between step S9102 and step S5101.

[0586] As an embodiment, the first bearer is suspended during the time interval between step S9102 and step S5101.

[0587] As an embodiment, when step S5101 is executed, the first bearer is suspended.

[0588] As an embodiment, before the step S6101 in embodiment 6, the step S9101 and the step S9102 are executed.

[0589] As an embodiment, the first bearer is not resumed within the time interval between step S9102 and step S6101.

[0590] As an embodiment, the first bearer is suspended during the time interval between step S9102 and step S6101.

[0591] As an embodiment, when step S6101 is executed, the first bearer is suspended.

[0592] Example 10

[0593] Embodiment 10 illustrates a structural block diagram of a processing device in a first node according to an embodiment of the present application, as shown in FIG10. In FIG10, the processing device 1000 in the first node includes a first receiver 1001 and a first transmitter 1002.

[0594] A first receiver 1001 receives a first MAC PDU, wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer;

[0595] The first transmitter 1002 discards the first MAC subPDU in response to receiving the first MAC PDU;

[0596] In embodiment 10, the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link;

[0597] or,

[0598] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0599] As an embodiment, the first RNTI is a G-RNTI; the non-unicast is a multicast; and the first MAC PDU is received via the first RNTI.

[0600] As an embodiment, the first logical identifier is unicast; and the first MAC PDU is received via a secondary link.

[0601] As an embodiment, the first MAC PDU is for MBS; the non-unicast is multicast; and the first MAC PDU is received via non-unicast.

[0602] As an embodiment, the first receiver 1001 receives a first RRC message; as a response to the reception of the first RRC message, maintains the RRC_INACTIVE state and suspends the first bearer; wherein the first RRC message indicates that data is transmitted through at least one bearer in the RRC_INACTIVE state; and the first bearer is a bearer other than the at least one bearer.

[0603] As an embodiment, the first receiver 1001 determines that a connection failure occurs; and suspends the first bearer in response to the determination of the connection failure.

[0604] As an embodiment, the first receiver 1001 includes at least one of the antenna 452 or the receiver 454 or the multi-antenna receiving processor 458 or the receiving processor 456 or the controller / processor 459 or the memory 460 or the data source 467 in FIG. 4 of the present application.

[0605] As an embodiment, the first receiver 1001 includes at least the antenna 452 and the receiver 454 in FIG. 4 of the present application.

[0606] As an embodiment, the first transmitter 1002 includes at least one of the antenna 452 or transmitter 454 or multi-antenna transmission processor 457 or transmission processor 468 or controller / processor 459 or memory 460 or data source 467 in FIG. 4 of the present application.

[0607] As an embodiment, the first transmitter 1002 includes at least the antenna 452 and the transmitter 454 in FIG. 4 of the present application.

[0608] Example 11

[0609] Embodiment 11 illustrates a structural block diagram of a processing device in a second node according to an embodiment of the present application, as shown in FIG11 . In FIG11 , the processing device 1100 in the second node includes a second transmitter 1101 .

[0610] The second transmitter 1101 sends a first MAC PDU, wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in response to receiving the first MAC PDU, the receiver of the first MAC PDU discards the first MAC subPDU;

[0611] In embodiment 11, the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link;

[0612] or,

[0613] The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

[0614] As an embodiment, the first RNTI is a G-RNTI; the non-unicast is a multicast; and the first MAC PDU is received via the first RNTI.

[0615] As an embodiment, the first logical identifier is unicast; and the first MAC PDU is received via a secondary link.

[0616] As an embodiment, the first MAC PDU is for MBS; the non-unicast is multicast; and the first MAC PDU is received via non-unicast.

[0617] As an embodiment, the second transmitter 1101 sends a first RRC message; wherein, as a response to the reception of the first RRC message, the receiver of the first MAC PDU maintains the RRC_INACTIVE state and suspends the first bearer; the first RRC message indicates that data is transmitted through at least one bearer in the RRC_INACTIVE state; the first bearer is a bearer other than the at least one bearer.

[0618] As an embodiment, the receiver of the first MAC PDU determines that a connection failure occurs; in response to the determination that a connection failure occurs, the receiver of the first MAC PDU suspends the first bearer.

[0619] As an embodiment, the second transmitter 1101 includes at least one of the antenna 420 or the transmitter 418 or the multi-antenna transmission processor 471 or the transmission processor 416 or the controller / processor 475 or the memory 476 in FIG. 4 of the present application.

[0620] As an embodiment, the second transmitter 1101 includes at least the antenna 420 and the transmitter 418 in FIG. 4 of the present application.

[0621] Those skilled in the art will appreciate that all or part of the steps in the above method can be completed by instructing 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 functional module. This application is not limited to any specific form of combination of software and hardware. The user equipment, terminal and UE in this 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) terminals, eMTC (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.

[0622] The above description is only a preferred embodiment of the present application and is not intended to limit the scope of protection of the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

Claims

1. A first node used for wireless communication, characterized in that: include: A first receiver receives a first MAC PDU, wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; a first transmitter, in response to receiving the first MAC PDU, discarding the first MAC subPDU; wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link; or, The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

2. The first node according to claim 1, wherein: The first RNTI is a G-RNTI; the non-unicast is multicast; and the first MAC PDU is received through the first RNTI.

3. The first node according to claim 1, wherein: The first logical identifier is unicast; the first MAC PDU is received through a secondary link.

4. The first node according to claim 1, characterized in that The first MAC PDU is for MBS; the non-unicast is multicast; and the first MAC PDU is received via non-unicast.

5. The first node according to any one of claims 1 to 4, characterized in that: include: The first receiver receives a first RRC message; In response to receiving the first RRC message, maintaining an RRC_INACTIVE state and suspending the first bearer; The first RRC message indicates that data is transmitted through at least one bearer in the RRC_INACTIVE state; and the first bearer is a bearer other than the at least one bearer.

6. The first node according to any one of claims 1 to 5, characterized in that: include: The first receiver determines that a connection failure occurs; In response to the determination that a connection failure has occurred, the first bearer is suspended.

7. A method in a first node for wireless communication, characterized in that: include: Receive a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; In response to receiving the first MAC PDU, discarding the first MAC subPDU; wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link; or, The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

8. A second node used for wireless communication, characterized in that: include: A second transmitter sends a first MAC PDU, wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in response to receiving the first MAC PDU, a receiver of the first MAC PDU discards the first MAC subPDU; wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link; or, The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

9. A method in a second node for wireless communication, characterized in that: include: Sending a first MAC PDU; wherein the first MAC PDU includes a first MAC subPDU, the first MAC subPDU indicates a first logical identifier, the first logical identifier is configured, and the first logical identifier is associated with a first bearer; in response to receiving the first MAC PDU, the receiver of the first MAC PDU discards the first MAC subPDU; wherein the discarding of the first MAC subPDU is dependent on the first bearer being suspended, wherein the first MAC PDU is received via non-unicast, and / or the first MAC PDU is received via a side link; or, The discarding of the first MAC subPDU is dependent on the first bearer being associated to an RNTI other than a first RNTI, wherein the first MAC PDU is received via the first RNTI.

Images